| 1 | Opening of the meeting | |
|---|---|---|
| R2-231442 | [Reserved] | MCC |
| R2-231443 | [Reserved] | MCC |
| R2-231444 | [Reserved] | MCC |
| R2-231445 | [Reserved] | MCC |
| 2.1 | Approval of the agenda | |
| R2-2309400 | Agenda for RAN2#123bis | Chairman |
| 2.2 | Approval of the report of the previous meeting | |
| R2-2309401 | RAN2#123 Meeting Report | MCC |
| 2.4 | Instructions | |
| R2-2311262 | Advices for WI CR writing | Ericsson |
| 2.5 | Others | |
| R2-2309402 | RAN2 Handbook | MCC |
| 4.1 | EUTRA corrections Rel-17 and earlier | |
| R2-2309763 | MAC correction on drx-InactivityTimer for eMTC UE | Xiaomi |
| R2-2309764 | MAC correction on drx-InactivityTimer for eMTC UE | Xiaomi |
| R2-2309778 | Correction on the UL HARQ RTT timer length | MediaTek Inc., Apple |
| R2-2309779 | Correction on the UL HARQ RTT timer length | MediaTek Inc., Apple |
| R2-2309780 | Correction on the UL HARQ RTT timer length | MediaTek Inc., Apple |
| R2-2311407 | MAC correction on drx-InactivityTimer for eMTC UE | Xiaomi |
| R2-2311408 | MAC correction on drx-InactivityTimer for eMTC UE | Xiaomi |
| R2-2311540 | MAC correction on drx-InactivityTimer for eMTC UE | Xiaomi |
| R2-2311541 | MAC correction on drx-InactivityTimer for eMTC UE | Xiaomi |
| 4.2 | NB-IoT and eMTC support for NTN Rel-17 | |
| R2-2310716 | Koffset handling during handover | Huawei, HiSilicon |
| R2-2310835 | Clarification on ul-SyncValidityDuration in SIB31 | ZTE Corporation, Sanechips |
| R2-2311310 | Clarification on ul-SyncValidityDuration in SIB31 | ZTE Corporation, Sanechips |
| R2-2311311 | Correction to 36.300 on Koffset handling during handover | Huawei, HiSilicon |
| R2-2311312 | Correction to 38.300 on Koffset handling during handover | Huawei, HiSilicon |
| R2-2311597 | Correction to 36.321 on Koffset handling during handover | Huawei, Ericsson, HiSilicon |
| 5.1.1 | Stage 2 and Organisational | |
| R2-2309448 | LS on report quantity parameter setting for CQI reporting with 1Tx (R4-2313998; contact: Anritsu) | RAN4 |
| R2-2311058 | Draft Reply LS on report quantity parameter setting for CQI reporting with 1Tx | Nokia, Nokia Shanghai Bell |
| R2-2311225 | Response to LS on report quantity parameter setting for CQI reporting with 1Tx | Ericsson |
| 5.1.1.1 | Other | |
| R2-2311205 | Stage 2 correction on description of IAB related to 5GC | Samsung |
| R2-2311206 | Stage 2 correction on description of IAB related to 5GC | Samsung |
| 5.1.2.1 | MAC | |
| R2-2309616 | MAC correction related to PDCCH monitoring-r16 | Huawei, HiSilicon |
| R2-2309617 | MAC correction related to PDCCH monitoring-r17 | Huawei, HiSilicon |
| R2-2309618 | Correction on the msgB-ResponseWindow configuration-r16 | Huawei, HiSilicon |
| R2-2309619 | Correction on the msgB-ResponseWindow configuration-r17 | Huawei, HiSilicon |
| R2-2309641 | MAC correction related to PDCCH monitor-r17 | Huawei, HiSilicon |
| R2-2309643 | Clarification on the msgB-ResponseWindow configuration-r17 | Huawei, HiSilicon |
| R2-2309838 | Correction on CSI reporting for DCP function | Huawei, HiSilicon |
| R2-2309839 | Correction on CSI reporting for DCP function | Huawei, HiSilicon |
| R2-2311570 | Correction on CSI reporting for DCP function | Huawei, HiSilicon |
| 5.1.3.1 | NR RRC | |
| R2-2309856 | Clarification on the condition of subband reporting | Samsung |
| R2-2309857 | Clarification on the condition of subband reporting | Samsung |
| R2-2310172 | Clarification of the presence condition for rsrp-ThresholdSSB-SUL | Qualcomm Incorporated |
| R2-2310173 | Clarification of the presence condition for rsrp-ThresholdSSB-SUL | Qualcomm Incorporated |
| R2-2310174 | Clarification of the presence condition for rsrp-ThresholdSSB-SUL | Qualcomm Incorporated |
| R2-2310883 | Clarification on including ssbFrequency in measurement report | Ericsson |
| R2-2310884 | RRM relaxation and HST measurements | Ericsson |
| R2-2310908 | Correction on SIB1 acquisition | Philips International B.V. |
| R2-2310910 | Correction on SIB1 acquisition | Philips International B.V. |
| R2-2310961 | Miscellaneous non-controversial corrections Set XX | Ericsson |
| R2-2310962 | Miscellaneous non-controversial corrections Set XX | Ericsson |
| R2-2310994 | On-demand SI request corrections | Nokia, Nokia Shanghai Bell |
| R2-2310995 | On-demand SI request corrections | Nokia, Nokia Shanghai Bell |
| R2-2311071 | On-demand SI request corrections | Nokia, Nokia Shanghai Bell |
| R2-2311193 | Discussion on lowest subband for CSI reporting | Ericsson |
| R2-2311196 | Clarification of lowest subband for CSI reporting. | Ericsson |
| R2-2311198 | Clarification of lowest subband for CSI reporting. | Ericsson |
| R2-2311199 | Clarification of lowest subband for CSI reporting. | Ericsson |
| R2-2311421 | LS on combination of HST and RRM relaxation | Ericsson |
| R2-2311435 | LS on combination of HST and RRM relaxation | RAN2 |
| 5.1.3.2 | UE capabilities | |
| R2-2309469 | Reply LS on intraBandENDC-Support (R4-2314746; contact: Ericsson) | RAN4 |
| R2-2309515 | Discussion on fallback exception for intra-band ENDC | OPPO |
| R2-2310125 | Clarification to fallback band combination rule | Nokia, Nokia Shanghai Bell |
| R2-2310126 | Clarification to fallback band combination rule in TS 38.306 | Nokia, Nokia Shanghai Bell |
| R2-2311047 | Clarification on the Intra-band Non-CA Capabilities Reporting | ZTE Corporation, Sanechips |
| R2-2311048 | Clarification to fallback band combination rule | Nokia, Nokia Shanghai Bell |
| 5.2 | NR V2X | |
| R2-2309678 | Correction of SL synchronisation measurement | OPPO |
| R2-2309773 | Corrections to random access cancellation criteria for sidelink BSR and CSI reporting | Samsung Electronics Co., Ltd |
| R2-2309774 | Corrections to random access cancellation criteria for sidelink BSR and CSI reporting | Samsung Electronics Co., Ltd |
| R2-2310055 | Correction on MAC layer for sidelink | ZTE Corporation, Sanechips |
| R2-2310056 | Correction on MAC layer for sidelink | ZTE Corporation, Sanechips |
| R2-2310118 | Impact of SL power class on cell selection and reselection | Ericsson |
| R2-2310357 | Correction on AM DRB header compresson for PC5 PDCP reestablishment | Apple |
| R2-2310358 | Correction on AM DRB header compresson for PC5 PDCP reestablishment | Apple |
| R2-2310439 | Correction of SL synchronisation measurement | OPPO |
| R2-2310977 | Correction on NR sidelink RRC | Philips International B.V. |
| R2-2310978 | Correction on NR sidelink RRC | Philips International B.V. |
| R2-2311490 | [AT123bis][101][V2X/SL] Rel-16 corrections (ZTE) | ZTE |
| R2-2311581 | Correction on MAC layer for sidelink | ZTE Corporation, Sanechips |
| R2-2311582 | Correction on MAC layer for sidelink | ZTE Corporation, Sanechips |
| 5.3.1 | General and Stage 2 corrections | |
| R2-2309620 | Correction to 38.305 on NR E-CID | Huawei, HiSilicon |
| R2-2309621 | Correction to 38.305 on E-CID r17 | Huawei, HiSilicon |
| 5.3.2 | Stage 3 corrections (RRC/LPP/MAC/capabilities) | |
| R2-2309622 | Correction to 38.331 on GNSS-ID r16 | Huawei, HiSilicon |
| R2-2309623 | Correction to 38.331 on GNSS-ID r17 | Huawei, HiSilicon |
| R2-2309624 | Correction to 37.355 on broadcast information element | Huawei, HiSilicon |
| R2-2309625 | Correction to 37.355 on broadcast information element-r16 | Huawei, HiSilicon |
| R2-2309626 | Correction to 37.355 on broadcast information element-r17 | Huawei, HiSilicon |
| R2-2309644 | Correction to 38.305 on E-CID r16 | Huawei, HiSilicon |
| R2-2309645 | Correction to 38.305 on E-CID r17 | Huawei, HiSilicon |
| R2-2309646 | Correction to 38.331 on GNSS-ID r16 | Huawei, HiSilicon |
| R2-2309647 | Correction to 38.331 on GNSS-ID r17 | Huawei, HiSilicon |
| R2-2309648 | Correction to 37.355 on broadcast information element-r15 | Huawei, HiSilicon |
| R2-2309649 | Correction to 37.355 on broadcast information element-r16 | Huawei, HiSilicon |
| R2-2309650 | Correction to 37.355 on broadcast information elementr-r17 | Huawei, HiSilicon |
| R2-2310849 | GNSS SSR corrections and notes | Ericsson |
| R2-2310850 | GNSS SSR corrections and notes | Ericsson |
| R2-2311370 | Correction to 38.331 on GNSS-ID r16 | Huawei, HiSilicon |
| R2-2311371 | Correction to 38.331 on GNSS-ID r17 | Huawei, HiSilicon |
| 5.4.3 | RRC corrections | |
| R2-2310740 | CR on Clarification of the ObtainCommonLocation field description | Ericsson |
| R2-2310741 | Mirror CR on Clarification of the ObtainCommonLocation field description | Ericsson |
| 6.1 | Common | |
| R2-2309610 | [Post123][044][NR17] independentGapConfig-maxCC (Qualcomm) | Qualcomm Korea |
| 6.1.1 | Stage 2 and Organisational | |
| R2-2309411 | LS on Rel-17 PUCCH repetition enhancements (R1-2308429; contct: Nokia) | RAN1 |
| R2-2309413 | Reply LS on K2 indication for multi-PUSCH (R1-2308446; contact: LGE) | RAN1 |
| R2-2309447 | LS on values in ReducedAggregatedBandwidth-r17 IE (TS 38.331) (R4-2313581; contact: Huawei) | RAN4 |
| R2-2309460 | Reply LS on monitoring of paging occasions for CG-SDT with HD-FDD Redcap UEs (R4-2314464; contact: MediaTek) | RAN4 |
| R2-2309470 | LS on higher power limit capability for inter-band UL DC (R4-2314886; contact: MediaTek) | RAN4 |
| R2-2309485 | Reply to LS addressing packet loss (S6-232609; contact: Ericsson) | SA6 |
| R2-2309541 | Corrections on data loss for MCPTT UE MBS multicast reception | ZTE, Sanechips, CBN |
| R2-2309542 | Discussion about SA6 LS on packet loss and delay issue during multicast MBS delivery (with draft LS) | ZTE, Sanechips, CBN |
| R2-2310684 | Paging subgrouping in case of abnormal scenario | Nokia, Nokia Shanghai Bell |
| R2-2311152 | Clarification for Mission Critical UEs | Ericsson |
| R2-2311153 | [Draft] Reply to LS addressing packet loss | Ericsson |
| R2-2311422 | Clarification on handling connections of mission critical UEs to avoid packet losses | Ericsson |
| R2-2311423 | [draft] Reply LS to SA6 addressing packet loss | ZTE |
| R2-2311424 | Reply LS on monitoring of paging occasions for CG-SDT with HD-FDD Redcap Ues | RAN2 |
| 6.1.2 | User Plane corrections | |
| R2-2309628 | Correction on the applicability of SDT for RA procedure | Huawei, HiSilicon |
| R2-2309906 | Correction to DRX mode of multicast session | TD Tech, Chengdu TD Tech |
| R2-2310464 | Corrections on the RACH without SSB for RedCap in 38.321 | Huawei, HiSilicon |
| R2-2310466 | Correction for the looped RACH case for RedCap | Huawei, HiSilicon, Mediatek |
| R2-2310709 | Correction on the condition of HARQ feedback generation and the condition of stopping drx-RetransmissionTimerDL | Huawei, ASUSTek, Samsung, CBN, HiSilicon |
| R2-2310958 | Discussion on selection procedure for CFRA and CBRA | Ericsson |
| R2-2311080 | Correction on SRI in IAB MAC CEs | ZTE, Sanechips |
| R2-2311182 | Correction on BFI_COUNTER at SCG activation | Nokia, Nokia Shanghai Bell |
| R2-2311183 | Correction on SCG activation | Nokia, Nokia Shanghai Bell |
| R2-2311207 | Correction on the applicability of SDT for RA procedure | Huawei, HiSilicon |
| R2-2311269 | Correction on SRI in IAB MAC CEs | ZTE, Sanechips |
| R2-2311282 | Corrections on the RACH without SSB for RedCap in 38.321 | Huawei, HiSilicon |
| R2-2311584 | Report of [AT123bis][005][R17 UP] R2-2310709 (Huawei) | Huawei, HiSilicon (rapporteur) |
| R2-2311585 | Correction on the condition of HARQ feedback generation and the condition of stopping drx-RetransmissionTimerDL | Huawei, ASUSTek, Samsung, CBN, HiSilicon |
| 6.1.3 | Control Plane corrections | |
| R2-2311192 | Clarification of configuration of transmissionComb in IE SRS-Resource | Ericsson |
| 6.1.3.1 | NR RRC | |
| R2-2309412 | Reply LS to RAN2 on introduction of one new RRC parameter and one new UE capability for Rel-17 (R2-2306892; contact: Qualcomm) | RAN1 |
| R2-2309785 | Correction to support autonomous change of UE channel bandwidth during RACH | Qualcomm France |
| R2-2309986 | Correction on Type1 HARQ-ACK codebook generation | Qualcomm Incorporated |
| R2-2309987 | Correction on Type1 HARQ-ACK codebook generation | Qualcomm Incorporated |
| R2-2310041 | 38.331 Corrections on PDCCH-ConfigCommon for PEI | Xiaomi Communications |
| R2-2310095 | Missing cell group indication to the measConfig variable for conditional reconfiguration release | Samsung |
| R2-2310115 | Correction to RRC for 71 GHz on multi-PUSCH | LG Electronics Inc., Ericsson, ASUSTeK, Nokia, Nokia Shanghai Bell, Samsung, Xiaomi, Huawei, HiSilicon |
| R2-2310116 | Further correction to RRC for 71 GHz on multi-PUSCH | Ericsson, Xiaomi, ASUSTeK, Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, Samsung, LG Electronics Inc |
| R2-2310117 | Further discussion on k2 for multi-PUSCH | Ericsson, Huawei, HiSilicon, LG Electronics Inc., ASUSTeK, Nokia, Nokia Shanghai Bell, Samsung, Xiaomi |
| R2-2310342 | Emergency call handling in RedCap in barred cells | Apple Inc, T-Mobile USA, Qualcomm Inc |
| R2-2310465 | Corrections on the search space for RedCap | Huawei, HiSilicon |
| R2-2310467 | Correction on the cell barring procedure for RedCap | Huawei, HiSilicon |
| R2-2310667 | Correction on RedCap initial DL/UL BWP | ZTE Corporation, Sanechips |
| R2-2310668 | Clarification on the meaning of nogap-noncsg | ZTE Corporation, Nokia, Sanechips |
| R2-2310710 | RRC corrections for MBS | Huawei, CBN, HiSilicon |
| R2-2310721 | Correction on RLM/BFD relaxation state reporting | Nokia, Nokia Shanghai Bell |
| R2-2310963 | Miscellaneous non-controversial corrections Set XX | Ericsson |
| R2-2311081 | Correction to sfnSchemPDCCH and sfnSchemePDSCH | LG Electronics Inc. |
| R2-2311110 | Correction of field description of sfnSchemePDCCH and sfnSchemePDSCH | LG Electronics |
| R2-2311123 | MBS-related corrections | Google Inc. |
| R2-2311151 | RLM and BFD relaxation state reporting | Ericsson |
| R2-2311209 | Corrections on PDCCH-ConfigCommon for PEI | Beijing Xiaomi Mobile Software |
| R2-2311213 | Correction on rsrp-ThresholdSSB in RACH Partitioning | vivo |
| R2-2311289 | Report of [AT123bis][806] RLM and BFD relaxation state reporting | CATT |
| R2-2311425 | Correction to support autonomous change of UE channel bandwidth during RACH | Qualcomm Incorporated |
| R2-2311426 | Corrections on the search space for RedCap | Huawei, HiSilicon |
| R2-2311427 | Correction on RLM/BFD relaxation state reporting | CATT |
| R2-2311434 | Correction on RedCap initial DL/UL BWP | ZTE Corporation, Sanechips |
| 6.1.3.2 | UE capabilities | |
| R2-2309803 | Correction on multicast MRB for MBS | MediaTek Inc. |
| R2-2309982 | Summary of email discussion Post123][043][NR17] UE caps Maximum aggregated bandwidth (Qualcomm) | Qualcomm Incorporated |
| R2-2309983 | Introduction of maximum aggregated bandwidth for FR1 inter-band CA and for FR2 intra-band CA | Qualcomm Incorporated |
| R2-2309984 | Introduction of maximum aggregated bandwidth for FR1 inter-band CA and for FR2 intra-band CA | Qualcomm Incorporated |
| R2-2309985 | UE capability parameter values for total/maximum aggregated BW | Qualcomm Incorporated |
| R2-2310127 | Correction to higherpowerlimit-r17 in TS 38.331 | Nokia, Nokia Shanghai Bell |
| R2-2310682 | Corrections on the RACH without SSB for RedCap in 38.306 | Huawei, HiSilicon |
| R2-2310732 | Clarification on UplinkTxSwitchingBandParameters | Huawei, HiSilicon |
| R2-2310866 | Clarification on higher power limit support for CA_DC | MediaTek Inc., Ericsson |
| R2-2310867 | Correction to support higher power limit capability for inter-band UL MR-DC | MediaTek Inc., Ericsson |
| R2-2310868 | Correction to support higher power limit capability for inter-band UL MR-DC | MediaTek Inc., Ericsson |
| R2-2310869 | [DRAFT] Reply LS on higher power limit capability for inter-band UL DC | MediaTek Inc., Ericsson |
| R2-2310945 | Correction to higherpowerlimit-r17 in TS 38.306 | Nokia, Nokia Shanghai Bell |
| R2-2310946 | Correction to disabling scaling factor for Cross-carrier scheduling | Ericsson |
| R2-2311045 | Consideration on the Aggregated Bandwidth for NR-DC | ZTE Corporation, Sanechips |
| R2-2311050 | Correction of the capability independentGapConfig-maxCC | Qualcomm Incorporated, Ericsson |
| R2-2311051 | Correction of the capability independentGapConfig-maxCC | Qualcomm Incorporated, Ericsson |
| R2-2311052 | introduction of the capability independentGapConfig-maxCC-EUTRA | Qualcomm Incorporated, Ericsson |
| R2-2311053 | introduction of the capability independentGapConfig-maxCC-EUTRA | Qualcomm Incorporated, Ericsson |
| R2-2311063 | Discussion on parameter multipleCORESET for RedCap UEs | Ericsson |
| R2-2311090 | Discussion on RA report and logged MDT report for RedCap UEs | Qualcomm Incorporated |
| R2-2311159 | Correction of the capability independentGapConfig-maxCC | Qualcomm Incorporated, Ericsson |
| R2-2311160 | Correction of the capability independentGapConfig-maxCC | Qualcomm Incorporated, Ericsson |
| R2-2311161 | Introduction of the capability independentGapConfig-maxCC-EUTRA | Qualcomm Incorporated, Ericsson |
| R2-2311162 | introduction of the capability independentGapConfig-maxCC-EUTRA | Qualcomm Incorporated, Ericsson |
| R2-2311168 | Introduction of the capability independentGapConfig-maxCC-EUTRA | Qualcomm Incorporated, Ericsson |
| R2-2311270 | [Post123][044][NR17] independentGapConfig-maxCC (Qualcomm) | Qualcomm Korea |
| R2-2311429 | Introduction of maximum aggregated bandwidth for FR1 inter-band CA and for FR2 intra-band CA | Qualcomm Incorporated |
| R2-2311430 | Introduction of maximum aggregated bandwidth for FR1 inter-band CA and for FR2 intra-band CA | Qualcomm Incorporated |
| R2-2311431 | [DRAFT] LS on the CA Aggregated BW capability signaling by the UE | Apple Inc |
| R2-2311432 | [DRAFT] Reply LS on higher power limit capability for inter-band UL DC | MediaTek Inc., Ericsson |
| R2-2311433 | Clarification on UplinkTxSwitchingBandParameters | Huawei, HiSilicon |
| R2-2311440 | LS on the CA Aggregated BW capability signaling by the UE | RAN2 |
| R2-2311441 | Reply LS on higher power limit capability for inter-band UL DC | RAN2 |
| 6.1.3.3 | Other | |
| R2-2309988 | Discussion on autonomous BWP switch for non-RedCap | Qualcomm Incorporated |
| 6.2.1 | Control plane and Stage-2 corrections | |
| R2-2309516 | Correction on SIB/Preconfiguration applicability | OPPO, ZTE |
| R2-2309918 | PC5 unicast link release timing correction in indirect to direct path switch case | MediaTek Inc |
| R2-2310035 | Correction on the PWS SIBs forwarding | CATT |
| R2-2310036 | Discussion on PWS Handling in L2 U2N Relay Scenario | CATT |
| R2-2310354 | Correction on the inclusion of sl-LocalID-Request in SUI | Apple |
| R2-2310493 | Miscellaneous corrections for SL relay | Huawei, HiSilicon |
| R2-2310494 | SL-RLC0 and SL-RLC1 handling during L2 Relay UE RRC reestablishment | Huawei, HiSilicon |
| R2-2310599 | Correction on SUI for sidelink relay | ZTE, Sanechips |
| R2-2310600 | Correction on TS 388.331 for sidelink discovery | ZTE, Sanechips |
| R2-2310701 | Handling of Relay UE’s reconfiguration failure | Nokia, Nokia Shanghai Bell |
| R2-2310758 | Preconfiguration applicability in relay scenarios | Nokia, Nokia Shanghai Bell |
| R2-2310816 | RRC corrections for measurement reporting event Y2 | China Telecom, Huawei, HiSilicon |
| R2-2310838 | Correction on sidelink relay RRC | Philips International B.V. |
| R2-2311220 | Correction on the SidelinkUEInformationNR message | Ericsson |
| R2-2311261 | Report of [Pre123bis][401][Relay] Rel-17 control plane corrections (Huawei) | Huawei |
| R2-2311379 | Correction on SIB/Preconfiguration applicability | OPPO, ZTE |
| R2-2311380 | RRC corrections for SL relay | Huawei, HiSilicon, CATT, Apple, ZTE, China Telecom, Philips International B.V., Lenovo |
| R2-2311382 | [AT123bis][419][Relay] Rel-17 relay 38.304 corrections (OPPO) | OPPO |
| 6.2.2 | User plane corrections | |
| R2-2309685 | Align terminology of PC5 Relay RLC channel | OPPO |
| R2-2310353 | Clarifications on the Destination Index usage in SL BSR | Apple |
| 6.3 | NR Non-Terrestrial Networks (NTN) | |
| R2-2309533 | Correction on Event D1 | OPPO |
| R2-2309652 | Correction on the Capability of TA Reporting | vivo |
| R2-2310715 | Triggering of TA Report during handover | Huawei, HiSilicon |
| R2-2310757 | Notes in the RRC release procedure for NR-NTN | Google Inc. |
| R2-2310964 | Clarification of UE configuration in TN and NTN | Ericsson |
| R2-2311241 | UTC reference point in NR NTN R17 | Ericsson |
| R2-2311293 | LS on Stage-2 CR for MIMO evolution | RAN2 |
| R2-2311313 | Notes in the RRC release procedure for NR-NTN | Google Inc. |
| R2-2311598 | Correction to 38.321 on Koffset handling during handover | Huawei, Ericsson, HiSilicon |
| 6.4.1 | Stage 3 corrections | |
| R2-2309609 | Correction of existing SSR IEs in A-GNSS for BDS system | CATT, CAICT, CMCC, China Telecom, China Unicom, Huawei, ZTE Corporation, MediaTek Inc., OPPO, xiaomi, vivo, Spreadtrum |
| R2-2309627 | Correction to UE capability for batch reporitng | Huawei, HiSilicon |
| R2-2309919 | Issue on dl-prs-ResourceSetPeriodicityReq-r17 | Samsung |
| R2-2309920 | Addition of reference SCS for dl-prs-ResourceSetPeriodicityReq-r17 | Samsung |
| R2-2310545 | Discussion on LocationMeasurementIndication procedure for positioning | ZTE Corporation |
| R2-2310575 | Correction on LocationMeasurementIndication procedure for positioning | ZTE Corporation |
| R2-2310616 | Clarification on the field description of dl-prs-ResourceSetPeriodicityReq | vivo |
| R2-2310644 | Correction to activated measurement gap and PPW | Huawei, HiSilicon |
| R2-2310693 | Correction of existing SSR IEs in A-GNSS for BDS system | CATT, CAICT |
| R2-2310851 | Missing finer periodicities than 1s and HA GNSS Metrics field description correction | Ericsson |
| R2-2310909 | Correction to UE TEG Capability | Qualcomm Incorporated |
| R2-2310913 | Updates for the consumption of posSIBs assistance data element | Ericsson, Intel Corporation |
| R2-2311263 | Correction of existing SSR IEs in A-GNSS for BDS system | CATT, CAICT, CMCC, China Telecom, China Unicom, Huawei, ZTE Corporation, MediaTek Inc., OPPO, xiaomi, vivo, Spreadtrum |
| R2-2311372 | Report of [AT123bis][415][POS] BDS B1C corrections (CATT) | CATT |
| R2-2311373 | [AT123bis][416][POS] dl-prs-ResourceSetPeriodicityReq clarification | vivo |
| R2-2311377 | Correction on LocationMeasurementIndication procedure for positioning | ZTE Corporation |
| R2-2311378 | Field description correction for HA-GNSS metrics | Ericsson |
| R2-2311572 | Correction of existing SSR IEs in A-GNSS for BDS system | CATT, CAICT, CMCC, China Telecom, China Unicom, Huawei, ZTE Corporation, MediaTek Inc., OPPO, xiaomi, vivo, Spreadtrum |
| 6.4.2 | Stage 2 corrections | |
| R2-2310852 | Updates for the consunmption of posSIBs assistance data element | Ericsson, Intel Corporation |
| R2-2310997 | Updates for the consumption of posSIBs assistance data element | Ericsson, Intel Corporation, AT&T |
| 6.5.1 | SON Corrections | |
| R2-2310742 | Logging previousPSCellId in case of SCG addition failure | Ericsson |
| R2-2310743 | Successful handover report is missing under ObtainCommonLocationInfo | Ericsson |
| 6.5.2 | MDT Corrections | |
| R2-2310363 | Corrections on extension of R17 AreaConfiguration | CATT |
| R2-2310364 | Corrections on extension of AreaConfiguration (Option1) | CATT |
| R2-2310526 | Correction on delay definitions for split DRB | Huawei, HiSilicon |
| 6.6 | NR Sidelink enhancements | |
| R2-2309686 | Adding default SL DRX configuration in determination procedure in 5.28.2 | OPPO, Lenovo, Qualcomm, vivo, ZTE |
| R2-2309748 | Miscellaneous corrections on TS 38.321 for SL enhancements | LG Electronics Inc. |
| R2-2309766 | Correction of TS 38.321 on SL DRX | Huawei, HiSilicon |
| R2-2309775 | Corrections to random access cancellation criteria for sidelink DRX command indication | Samsung Electronics Co., Ltd |
| R2-2309812 | Miscellaneous correction on TS 38.331 for NR sidelink | Xiaomi |
| R2-2309813 | Miscellaneous correction on TS 38.321 for NR sidelink | Xiaomi |
| R2-2310057 | Correction on MAC layer for sidelink enhancement | ZTE Corporation, Sanechips |
| R2-2310119 | Correction to 38321 on SL IUC | Ericsson |
| R2-2310146 | PUCCH transmission for SL grants outside DRX active Time | Lenovo, Interdigital |
| R2-2310355 | Discussion on report of SL-DRX reject to gNB | Apple |
| R2-2310356 | Corrections on initiation and transmission of SUI reporting to gNB | Apple |
| R2-2310618 | Correction on SL IUC | Huawei, HiSilicon |
| R2-2311033 | Correction on NR sidelink RRC | Philips International B.V. |
| R2-2311149 | discussion on the field description related to CBR-based transmission | Sharp |
| R2-2311150 | CR for correction on field description related to CBR-based transmission | Sharp |
| R2-2311208 | Summary on RRC corrections for SL enhancements | Huawei, HiSilicon |
| R2-2311254 | Summary on RRC corrections for SL enhancements | Huawei, HiSilicon |
| R2-2311491 | Summary on [AT123bis][102][V2X/SL] Rel-17 RRC corrections (Huawei) | Huawei, HiSilicon |
| R2-2311492 | Misc RRC corrections for SL enhancements | Huawei |
| R2-2311493 | Summary of [AT123bis][103][V2XSL] Rel-17 MAC corrections (LG) | LG |
| R2-2311494 | Rel-17 MAC corrections | LG |
| R2-2311503 | Offline-110 summary | Apple |
| 7.0.1 | UE Capabilites | |
| R2-2309417 | LS on Rel-18 RAN1 UE features list for NR after RAN1#114 (R1-2308523; contact: NTT DOCOMO, AT&T) | RAN1 |
| R2-2310023 | Running UE capability CR on 38.306 for Rel-18 R1 R4 feature lists | Intel Corporation |
| R2-2310024 | Running UE capability CR on 38.331 for Rel-18 R1 R4 feature lists | Intel Corporation |
| 7.0.2 | CCCH LCID extension | |
| R2-2309512 | Discussion on CCCH LCID extension | OPPO |
| R2-2309568 | Discussion on Common Solution for Signalling Extension | vivo |
| R2-2309651 | LCID extension for CCCH | Samsung |
| R2-2309754 | Discussion on LCID extension | CATT |
| R2-2310004 | Overview of solutions for LCID extension | Huawei, HiSilicon |
| R2-2310030 | Discussion on extension mechanisms for RACH message 3 | Intel Corporation |
| R2-2310105 | LCID extension for CCCH | ZTE Corporation, Sanechips |
| R2-2310244 | Discussion on the LCID extension | CMCC |
| R2-2310305 | Views on CCCH LCID extension | Apple |
| R2-2310441 | Discussion on LCID extension | LG Electronics Inc. |
| R2-2310474 | Views on NR CCCH and/or LCID extension | Qualcomm Incorporated |
| R2-2310610 | Limited number of LCIDs | Vodafone GmbH |
| R2-2310724 | Considerations on LCID extension for CCCH | NEC |
| R2-2311184 | LCID extension for CCCH | Nokia, Nokia Shanghai Bell |
| R2-2311247 | Early indications and LCID space extension | Ericsson |
| 7.0.3 | Other | |
| R2-2309434 | LS on Rel-18 higher-layers parameter list (R1-2308674; contact: Ericsson) | RAN1 |
| 7.1 | NR network-controlled repeaters | |
| R2-2309404 | Reply LS on applicability of UAC for Network Controlled Repeater (C1-236447; contact: Samsung) | CT1 |
| R2-2310717 | Stage 2 corrections on NCR | Huawei, HiSilicon |
| R2-2310898 | Introducing support for Network-Controlled Repeaters to 38.300 | Ericsson |
| R2-2310899 | Clarification on number of beam index IDs for NCR | Ericsson |
| R2-2311037 | On RRC inactive and re-establishment mobility for NCR | Samsung, China Telecom, AT&T |
| R2-2311173 | Introducing support for Network Controlled Repeaters to 38.321 | Samsung |
| R2-2311480 | [AT123bis][751][NCR] Corrections (Apple) | Apple (Moderator) |
| R2-2311481 | Introducing support for Network Controlled Repeaters to 38.321 | Samsung |
| 7.2.1 | Organizational | |
| R2-2309406 | LS on LPP message and supplementary service event report over a user plane connection between UE and LMF (C1-236562; contact: Ericsson) | CT1 |
| R2-2309409 | Reply LS on LPHAP (R1-2308349; contact: Huawei) | RAN1 |
| R2-2309419 | LS on Priority Handling for SL Positioning (R1-2308559; contact: Intel) | RAN1 |
| R2-2309423 | LS on the longer PRS/SRS periodicity for LPHAP (R1-2308571; contact: Huawei) | RAN1 |
| R2-2309427 | Reply LS on PRU Procedures (R1-2308644; contact: CATT) | RAN1 |
| R2-2309428 | LS on TRP ID for positioning with bandwidth aggregation (R1-2308646; contact: ZTE) | RAN1 |
| R2-2309429 | LS on RSRP based TA validation for LPHAP (R1-2308649; contact: Huawei) | RAN1 |
| R2-2309430 | LS on the resource selection window for Scheme 2 in a dedicated resource pool for positioning (R1-2308651; contact: Qualcomm) | RAN1 |
| R2-2309452 | Reply LS on single measurement gap for DL PRS with Rx Hopping (R4-2314357; contact: Xiaomi) | RAN4 |
| R2-2309453 | LS on SL positioning and CPP measurements report mapping (R4-2314358; contact: CATT) | RAN4 |
| R2-2309454 | Reply LS on LPHAP (R4-2314360; contact: Huawei) | RAN4 |
| R2-2309465 | LS on PRS/RRM measurement when eDRX cycle > 10.24s (R4-2314483; contact: Ericsson) | RAN4 |
| R2-2309474 | Response LS to RAN WG2 on reporting positioning measurements taken in RRC_IDLE (S2-2309926; contact: CATT) | SA2 |
| R2-2309477 | Reply LS on Reply LS on security aspects for Ranging/Sidelink Positioning (S2-2310025; contact: Xiaomi) | SA2 |
| R2-2309596 | Work Plan for Rel-18 WI on Expanded and Improved NR Positioning | CATT, Intel Corporation, Ericsson |
| R2-2309597 | Reply LS to SA2 on reporting positioning measurements taken in RRC_IDLE | CATT |
| R2-2309598 | [Draft]Reply LS on Reply LS on PRU Procedures | CATT |
| R2-2309599 | Reply LS on TRP ID for positioning with bandwidth aggregation | CATT |
| R2-2309600 | LPP running CR for LPHAP | CATT |
| R2-2309601 | LPP running CR for Carrier Phase Positioning | CATT |
| R2-2309602 | LPP Running CR for bandwidth aggregation | CATT |
| R2-2309603 | LPP running CR for RAT-dependent integrity | CATT |
| R2-2309604 | LPP Running CR for Redcap positioning | CATT |
| R2-2309632 | Running MAC CR for LPHAP | Huawei, HiSilicon |
| R2-2309633 | Running MAC CR for Sidelink Positioning | Huawei, HiSilicon |
| R2-2309635 | Running MAC CR for CA positioniing | Huawei, HiSilicon |
| R2-2309636 | Running MAC CR for REDCAP positioning | Huawei, HiSilicon |
| R2-2309637 | Draft reply LS on LPHAP TA validation | Huawei, HiSilicon |
| R2-2309667 | Running 38300 CR for sidelink positioning | vivo |
| R2-2310218 | Further considerations on SLPP specification | Intel Corporation |
| R2-2310219 | TS38.355 TP on SLPP session and session procedure | Intel Corporation |
| R2-2310220 | TS38.355 TP on ASN.1 part | Intel Corporation |
| R2-2310221 | TS38.355 TP on SLPP procedure | Intel Corporation |
| R2-2310222 | TS 38.355 v1.1.0 | Intel Corporation |
| R2-2310444 | Discussion on R18 positioning UE capabilities | Beijing Xiaomi Mobile Software |
| R2-2310860 | Rapporteur CR for Sidelink Positioning RRC Changes | Ericsson |
| R2-2310861 | Rapporteur CR for CPP Positioning RRC Changes | Ericsson |
| R2-2310862 | Rapporteur CR for Redcap Positioning RRC Changes | Ericsson |
| R2-2310863 | Rapporteur CR for bandwidth aggregation | Ericsson |
| R2-2310864 | Running RRC CR for Positioning | Ericsson |
| R2-2310911 | Running Stage 2 CR for 'Expanded and improved NR positioning' | Qualcomm Incorporated |
| R2-2310980 | Running CR for Positioning | Ericsson |
| R2-2311265 | [draft] Reply LS on PRS/RRM measurement when eDRX cycle > 10.24s | Ericsson |
| R2-2311375 | Reply LS on R1-2308644 for CPP | RAN2 |
| R2-2311376 | [AT123bis][402][POS] PRUs (CATT) | CATT |
| R2-2311381 | Reply LS to SA2 on reporting positioning measurements taken in RRC_IDLE | RAN2 |
| R2-2311386 | LS on extended PRS and SRS periodicity | RAN2 |
| R2-2311387 | [Draft] LS on TA validation for LPHAP | Huawei, HiSilicon |
| R2-2311388 | Summary of [AT123bis][428][POS] LS to RAN1 and RAN4 on TA validation for LPHAP | Huawei, HiSilicon |
| R2-2311389 | Reply LS on the resource selection window for Scheme 2 in a dedicated resource pool for positioning | RAN2 |
| R2-2311390 | Summary of [AT123bis][426][POS] Rel-18 positioning capabilities (Xiaomi) | Xiaomi |
| R2-2311396 | LPP running CR for RAT-dependent integrity | CATT |
| R2-2311397 | LPP running CR for Carrier Phase Positioning | CATT |
| R2-2311398 | LPP Running CR for bandwidth aggregation | CATT |
| R2-2311399 | LPP running CR for LPHAP and Redcap positioning | CATT |
| R2-2311536 | Reply LS on INACTIVE eDRX above 10.24sec and SDT (R3-235765; contact: Ericsson) | RAN3 |
| R2-2311550 | [AT123bis][403][POS] LPP CRs (CATT) | 11407 |
| R2-2311551 | Running MAC CR for Sidelink Positioning | Huawei, HiSilicon |
| R2-2311552 | Running CR for Positioning | Ericsson |
| R2-2311553 | [AT123][405][POS] Positioning RRC CRs (Ericsson) | Ericsson |
| R2-2311554 | Running Stage 2 CR for 'Expanded and improved NR positioning' | Qualcomm Incorporated |
| R2-2311555 | Running 38300 CR for sidelink positioning | vivo |
| R2-2311563 | Running MAC CR for LPHAP | Huawei, HiSilicon |
| R2-2311564 | Summary of [AT123bis][404][POS] Positioning MAC CRs (Huawei) | Huawei, HiSilicon |
| R2-2311565 | Reply LS on R1-2308644 for CPP | RAN2 |
| R2-2311567 | Summary of [AT123bis][406][POS] Positioning 38.305 CR (Qualcomm) | Qualcomm Incorporated |
| R2-2311568 | LS on TA validation for LPHAP | RAN2 |
| 7.2.2 | Sidelink positioning | |
| R2-2309578 | UE Positioning using Sidelink | Fraunhofer IIS, Fraunhofer HHI |
| R2-2309605 | SLPP and RRC Signaling Design for SL positioning | CATT |
| R2-2309630 | Discussion on higher layer aspects for sidelink positioning | Huawei, HiSilicon |
| R2-2309631 | Discussion on lower layer aspects for SL positioning | Huawei, HiSilicon |
| R2-2309634 | Summary of [Post123][403][POS] Sidelink positioning MAC issues (Huawei) | Huawei, HiSilicon |
| R2-2309668 | Remaining issues on higher layer aspects for sidelink positioning | vivo |
| R2-2309669 | Discussion on transmission and measurement of SL-PRS | vivo |
| R2-2309741 | Further discussion on SL positioning and ranging | CEWiT |
| R2-2309759 | Discussion on SL positioning | Xiaomi |
| R2-2310014 | Discussion on sidelink positioning | Spreadtrum Communications |
| R2-2310044 | Discussion on UE assistance information for SL-PRS | Samsung Electronics Co., Ltd |
| R2-2310076 | Open issues regarding SLPP session | Samsung Guangzhou Mobile R&D |
| R2-2310194 | SLPP signalling and procedures | MediaTek Inc. |
| R2-2310195 | SLPP information forwarding | MediaTek Inc. |
| R2-2310216 | Report of [Post123][401][POS] RAN2 impact from SL-PRS parameters (Intel) | Intel Corporation |
| R2-2310217 | Further considerations on sidelink positioning | Intel Corporation |
| R2-2310275 | Considerations on Sidelink positioning | CMCC |
| R2-2310347 | UE only SL positioning procedure | Apple |
| R2-2310379 | Further discussion on sidelink positioning | OPPO |
| R2-2310429 | Remaining issues on higher layer aspects for R18 sidelink positioning | LG Electronics Inc. |
| R2-2310430 | Remaining issues on lower layer aspects for R18 sidelink positioning | LG Electronics Inc. |
| R2-2310436 | Discussion on sidelink positioning | InterDigital, Inc. |
| R2-2310541 | Discussion on lower-layer related sidelink positioning | ZTE Corporation |
| R2-2310543 | Discussion on sidelink positioning | ZTE Corporation |
| R2-2310680 | Discussion of resource allocation aspects | Nokia Netherlands |
| R2-2310691 | Discussion of SLPP / LPP signalling procedures | Nokia Netherlands |
| R2-2310759 | Considerations on multiplexing, congestion control and ARP | Sony |
| R2-2310789 | SL Positioning Discussion | Lenovo |
| R2-2310833 | Further discussion on sidelink positioning | ROBERT BOSCH GmbH |
| R2-2310848 | Discussion of session management for SL positioning | Nokia Netherlands |
| R2-2310856 | Remaining issue for NW involved Sidelink positioning | Ericsson |
| R2-2310912 | Further Considerations on SLPP Design | Qualcomm Incorporated |
| R2-2311032 | On sidelink positioning discovery and capabilities exchange | Philips International B.V. |
| R2-2311035 | On the stability of Anchor UE location | Philips International B.V. |
| R2-2311374 | [AT123bis][401][POS] Progressing TS 38.355 (Intel) | Intel Corporation |
| R2-2311383 | Summary of [AT123bis][428][POS] Discussion of SL positioning MAC issues (Huawei) | Huawei, HiSilicon |
| R2-2311599 | Reply LS on Priority Handling for SL Positioning | RAN2 |
| 7.2.3 | RAT-dependent integrity | |
| R2-2309924 | Discussion on RAT-dependent integrity | Lenovo |
| R2-2310380 | Consideration on RAT-dependent positioning integrity | OPPO |
| R2-2310415 | Discussion on RAT-dependent positioning integrity | Xiaomi |
| R2-2310823 | Discussion on RAT dependent integrity | InterDigital Inc. |
| R2-2310857 | Support for UE-based integrity | Ericsson |
| R2-2310914 | Remaining Issues for Integrity of NR Positioning Technologies | Qualcomm Incorporated |
| R2-2310996 | Signalling about beam related information for positioning integrity | Nokia, Nokia Shanghai Bell |
| 7.2.4 | LPHAP | |
| R2-2309579 | Reliable LPHAP position with extended DRX cycle | Fraunhofer IIS, Fraunhofer HHI |
| R2-2309606 | Discussion on LPHAP | CATT |
| R2-2309629 | Discussion on LPHAP | Huawei, HiSilicon |
| R2-2309670 | Remaining issues of LPHAP | vivo |
| R2-2309922 | Discussion on alignment between (e)DRX and PRS | Samsung |
| R2-2309923 | Discussion on SRS configuration in RRC_INACTIVE | Samsung |
| R2-2309925 | Discussion on low power high accuracy positioning | Lenovo |
| R2-2310223 | Further considerations on LPHAP | Intel Corporation |
| R2-2310276 | Further considerations on LPHAP | CMCC |
| R2-2310381 | Discussion on the leftover issues of LPHAP enhancement | OPPO |
| R2-2310416 | Discussion on LPHA positioning | Xiaomi |
| R2-2310540 | Discussion on LPHAP | ZTE Corporation |
| R2-2310760 | Considerations on Low Power High Accuracy Positioning | Sony |
| R2-2310824 | Discussion on LPHAP | InterDigital Inc. |
| R2-2310858 | Remaining issue on Low Power High Accuracy Positioning | Ericsson |
| R2-2310915 | Remaining issues for LPHAP | Qualcomm Incorporated |
| 7.2.5 | RedCap positioning, carrier phase positioning, and bandwidth aggregation for positioning | |
| R2-2309607 | Discussion on bandwidth aggregation for positioning | CATT |
| R2-2309608 | LPP and RRC impacts to enable Carrier Phase Positioning | CATT |
| R2-2309671 | RAN2-related issues about bandwidth aggregation | vivo |
| R2-2309893 | Discussion on RAN1 led positioning topics | Huawei, HiSilicon |
| R2-2309926 | Discussion on RedCap positioning, carrier phase positioning and PRS/SRS bandwidth aggregation | Lenovo |
| R2-2310346 | On PRS bandwidth aggregation | Apple |
| R2-2310417 | Discussion on carrier phase positioning and bandwidth aggregation for positioning | Xiaomi |
| R2-2310542 | Discussion on BW aggregation and RedCap positioning | ZTE Corporation |
| R2-2310761 | Discussion on Frequency hopping for Positioning for RedCap Ues | Sony |
| R2-2310825 | Discussion on positioning for RedCap positioning, carrier phase positioning, and bandwidth aggregation for positioning | InterDigital Inc. |
| R2-2310859 | Discussion based upon RAN1 agreements on CPP, RedCap, Bandwidth aggregation | Ericsson |
| R2-2310916 | Configuration Enhancements for DL-PRS Aggregation | Qualcomm Incorporated |
| R2-2310998 | [Post123][402][POS] RAN2 impact of RAN1-led positioning objectives (Nokia) | Nokia, Nokia Shanghai Bell |
| R2-2311391 | LS on request for clarifications on RedCap positioning, carrier phase positioning, and bandwidth aggregation for positioning | RAN2 |
| 7.3.1 | Organizational | |
| R2-2310001 | Report of [POST123][312][NES] Running CR 38.331 (Huawei) | Huawei, HiSilicon |
| R2-2310002 | Running 38.331 CR - Introduction of Network energy savings for NR | Huawei, HiSilicon |
| R2-2310003 | Discussion on remaining issues of the RRC CR for NES | Huawei, HiSilicon |
| R2-2310233 | Running CR to 38.321 for Network Energy Savings | InterDigital |
| R2-2310234 | MAC open issues for NES | InterDigital |
| R2-2310235 | Summary of [Post123][314][NES] 38.321 Running CR (InterDigital) | InterDigital |
| R2-2310288 | Running 38.304 CR - Introduction of Network energy savings for NR | Apple |
| R2-2310289 | Open issues of running 38.304 CR for NES | Apple |
| R2-2310407 | Work plan for NR network energy savings | Huawei, HiSilicon |
| R2-2310793 | MAC CE for SP CSI reporting on PUCCH | Nokia, Nokia Shanghai Bell |
| R2-2310947 | Running CR to 38300 for Network energy savings | Ericsson |
| R2-2310948 | Open issues for NES on 38.300 | Ericsson |
| R2-2311578 | LS on cell DTX/DRX operations (R1-2310476; contact: Intel) | RAN1 |
| 7.3.2 | DTX/DRX mechanism | |
| R2-2309518 | Discussion on Cell DTX/DRX configuration and operation | Xiaomi |
| R2-2309574 | Various (RRC Procedure, Measurement, SR, CG etc.) alignment aspects | Lenovo |
| R2-2309742 | Cell DTX/DRX NES Techniques | CEWiT |
| R2-2309772 | Remaining issues for Cell DTX_DRX | Samsung Electronics Co., Ltd |
| R2-2309992 | Remaining issues on cell DTX-DRX | vivo |
| R2-2309998 | Discussion on remaining issues of cell DTX and DRX | Huawei, HiSilicon |
| R2-2310077 | Leftover issues of Cell DTX/DRX | CATT, Turkcell |
| R2-2310229 | Remaining issues on Cell DTX/DRX | InterDigital |
| R2-2310262 | Discussion on cell DTX/DRX | CMCC |
| R2-2310290 | Remaining key open issues of Cell DTX / DRX | Apple |
| R2-2310382 | Discussion on DTX/DRX mechanism | OPPO |
| R2-2310451 | Discussion on Cell-DTX/DRX and aligned C-DRX configurations | NEC |
| R2-2310479 | SPS and Multicast Impacts of Cell DTX/DRX | Samsung |
| R2-2310482 | Cell DTX/DRX NES Techniques | III |
| R2-2310546 | Discussion on Cell DRX/DTX activation and deactivation | Sharp |
| R2-2310553 | Remaining issues of Cell DTXDRX | ZTE Corporation, Sanechips |
| R2-2310558 | Discussion on Cell DTX and DRX activation | Vodafone GmbH |
| R2-2310577 | Remaining issues on Cell DTX/DRX | Fujitsu |
| R2-2310685 | Remaining issues on Cell DTX/DRX | Nokia, Nokia Shanghai Bell |
| R2-2310694 | Single configuration with multiple DTX_DRX patterns and explicit signalling | BT Plc, Nokia, Nokia Shanghai Bell, T-Mobile, Deutsche Telekom, NTT Docomo, KDDI, ZTE |
| R2-2310699 | Discussion on DTX/DRX mechanism | LG Electronics Inc. |
| R2-2310870 | Remaining RRC issues of Cell DTX and DRX mechanism | MediaTek Inc. |
| R2-2310949 | Open issues for NW DTX-DRX | Ericsson |
| R2-2310956 | Cell DTX-DRX Mechanism | Qualcomm Incorporated |
| R2-2310982 | UL considerations for Cell DTX/DRX | NEC Telecom MODUS Ltd. |
| R2-2311166 | Key open issues on Cell DTX/DRX | Fraunhofer IIS, Fraunhofer HHI |
| R2-2311224 | Single configuration with multiple DTX_DRX patterns and explicit signalling | BT Plc, Nokia, Nokia Shanghai Bell, T-Mobile, Deutsche Telekom, NTT Docomo, KDDI, ZTE, Turkcell |
| R2-2311226 | Single configuration with multiple DTX_DRX patterns and explicit signalling | BT Plc, Nokia, Nokia Shanghai Bell, T-Mobile, Deutsche Telekom, NTT Docomo, KDDI, ZTE, Turkcell |
| R2-2311235 | UE C-DRX configuration used upon cell DTX activation | vivo, Fraunhofer IIS, Huawei, HiSilicon, LG Electronics Inc., MediaTek Inc., NEC, Xiaomi, ZTE Corporation, Ericsson, Nokia, Nokia Shanghai Bell, BT Plc, NTT DOCOMO INC. |
| R2-2311260 | Key open issues on Cell DTX/DRX | Fraunhofer IIS, Fraunhofer HHI |
| R2-2311285 | Summary of [AT123bis][003][NES] Offline discussion (InterDigital) | InterDigital |
| 7.3.3 | SSB-less Scell operation | |
| R2-2309952 | Discuss on SSB-less SCell operation in NES | Lenovo |
| R2-2310078 | Enhancements on SSB-less SCell operation | CATT |
| R2-2310231 | SSB-less Scell operation | InterDigital |
| R2-2310291 | Further discussion on RAN2 work of inter-band SSB-less CA | Apple |
| R2-2310383 | Discussion on SSB-less Scell operation | OPPO |
| R2-2310554 | Discussion on SSB-less SCell operation for NES | ZTE Corporation, Sanechips |
| 7.3.4 | Cell selection/re-selection | |
| R2-2309517 | False paging reduction in NES cell | Xiaomi |
| R2-2309572 | Intra frequency reselections and cell barring | Lenovo |
| R2-2309796 | Discussion on Cell Selection and Reselection for NES | Samsung |
| R2-2309993 | Discussion on cell selection/re-selection | vivo |
| R2-2309999 | Discussion on remaining issues of cell barring for NES | Huawei, HiSilicon |
| R2-2310079 | Consideration on Cell Selection/Re-selection on NES cells | CATT, Turkcell |
| R2-2310292 | Remaining issues of legacy UE barring | Apple |
| R2-2310384 | Discussion on cell selection reselection | OPPO |
| R2-2310555 | Consideration on cell access restrictions for NES | ZTE Corporation, Sanechips |
| R2-2310794 | Reselection and Paging handling for NES | Nokia, Nokia Shanghai Bell |
| R2-2310871 | Remaining NES issues on 38.304 | MediaTek Inc. |
| R2-2310950 | Remaining aspects for NES Cell selection/reselection | Ericsson |
| R2-2310957 | Barring legacy UEs for NES Cells | Qualcomm Incorporated |
| R2-2311072 | Discussion on Cell selection | NTT DOCOMO INC. |
| R2-2311079 | On the need of notBarred for cellBarredNES field | LG Electronics |
| R2-2311158 | Remaining Issues on Cell Selection and Re-Selection for NES | Fraunhofer IIS, Fraunhofer HHI |
| 7.3.5 | Connected mode mobility | |
| R2-2309519 | Discussion on NES in SCG | Xiaomi |
| R2-2309573 | Source and Target side CHO Procedures | Lenovo |
| R2-2309797 | Discussion on Connected mode mobility for NES | Samsung |
| R2-2309868 | Deactivation and activation of a CHO event for NES | Google Inc. |
| R2-2309991 | CHO enhancement for NES cell | Quectel |
| R2-2309994 | Discussion on CHO enhancement for target cell in NES mode | vivo |
| R2-2310080 | CHO procedure enhancements | CATT |
| R2-2310230 | CHO for NES | InterDigital |
| R2-2310263 | Discussion on CHO enhancements for NES | CMCC |
| R2-2310293 | Remaining issues of NES specific CHO enhancement | Apple |
| R2-2310385 | Discussion on connected mode mobility | OPPO |
| R2-2310408 | Discussion on CHO enhancement for NES | Huawei, HiSilicon, Turkcell |
| R2-2310438 | Discussions on CHO for NES | KDDI Corporation, BT Plc |
| R2-2310547 | Discussion on CHO enhancements for NES | Sharp |
| R2-2310556 | The remaining issues on connected mode mobility | ZTE Corporation, Sanechips |
| R2-2310578 | Remaining issues on Connected mode mobility for NES | Fujitsu |
| R2-2310725 | Further considerations on CHO enhancement | NEC |
| R2-2310762 | Handover enhancement for NES | Sony |
| R2-2310795 | CHO on NES | Nokia, Nokia Shanghai Bell |
| R2-2310960 | NES Connected mode mobility | Qualcomm Incorporated, InterDigital, vivo, Sharp, Sony |
| R2-2310984 | Considerations on CHO configured with target NES cell | NEC Telecom MODUS Ltd. |
| R2-2311129 | CHO enhancement for different NES use cases | LG Electronics inc. |
| R2-2311136 | Discussion on CHO for NES | Ericsson |
| R2-2311577 | [DRAFT] LS on NES CHO and Cell DTX/DRX | Apple |
| R2-2311589 | LS on NES CHO | RAN2 |
| 7.3.6 | Others | |
| R2-2309520 | Discussion on sub-configuration for power adaption and spatial adaption | Xiaomi |
| R2-2310409 | Discussion on RAN1 and RAN3 led NES techniques | Huawei, HiSilicon |
| R2-2310865 | SP CSI reporting on PUCCH Activation MAC CE | InterDigital |
| R2-2310968 | Restricting Paging to limited area | Qualcomm Incorporated |
| R2-2311140 | MAC CE for NES | Ericsson |
| R2-2311534 | Reply LS on paging | RAN2 |
| R2-2311591 | Reply LS on paging | RAN2 |
| 7.4.1 | Organizational Stage-2 and UE caps | |
| R2-2309414 | Reply LS on L1 measurements for LTM (R1-2308465; contact: Ericsson) | RAN1 |
| R2-2309426 | LS on L1 measurement and TA management for LTM (R1-2308625; contact: CATT, Fujitsu, MediaTek) | RAN1 |
| R2-2309457 | Reply LS on PDCCH order RACH on neighbour cell (R4-2314454; contact: CATT) | RAN4 |
| R2-2309458 | Reply LS on beam application time and UE based TA measurement for LTM (R4-2314455; contact: Ericsson | RAN4 |
| R2-2309543 | RRC Running CR for CHO with candidate SCGs | CATT |
| R2-2309544 | RRC Open issue list for CHO with candidate SCGs | CATT |
| R2-2309830 | 37.340 running CR for introduction of NR further mobility enhancements | ZTE Corporation, Sanechips |
| R2-2309832 | Open issue list on 37.340 running CR | ZTE Corporation, Sanechips |
| R2-2310028 | 38.306 running draftCR for introduction of NR further mobility enhancements | Intel Corporation |
| R2-2310029 | 38.331 running draftCR for UE capability of NR further mobility enhancements | Intel Corporation |
| R2-2310033 | Discussion on L2/3 UE capabilities for NR further mobility enhancements | Intel Corporation |
| R2-2310360 | 38.300 running CR for introduction of NR further mobility enhancements | MediaTek Inc., vivo |
| R2-2310361 | Stage-2 TP for Early Synchronization | MediaTek Inc. |
| R2-2310375 | RRC running CR for subsequent CPAC in NR-DC | OPPO |
| R2-2310376 | RRC open issues list for subsequent CPAC in NR-DC | OPPO |
| R2-2310885 | RRC running CR for LTM | Ericsson |
| R2-2310886 | RRC open issues list for LTM | Ericsson |
| R2-2311000 | UE capability for LTM and leftover stage 2 issues | Huawei, HiSilicon |
| R2-2311330 | Summary of [AT123bis][511][feMob] Stage-2 TP for Early Synchronization(MTK) | MediaTek Inc. |
| R2-2311610 | 38.300 running CR for introduction of NR further mobility enhancements | MediaTek Inc., vivo |
| 7.4.2.1 | Control Plane and RRC | |
| R2-2309580 | L1 measurement report to support LTM | NEC |
| R2-2309581 | RB Reconfig for MCG LTM and Clarification on SCG LTM | NEC |
| R2-2309710 | Discussion on RRC centric open issues | LG Electronics |
| R2-2309719 | Discussion on LTM procedures | vivo |
| R2-2309720 | RRC configuration for LTM | vivo |
| R2-2309787 | Configuration for UE based RACH-less LTM and sequential measurement | Futurewei |
| R2-2309833 | Consideration on LTM in NR-DC | ZTE Corporation, Sanechips |
| R2-2309834 | Remaining issues on LTM RRC | ZTE Corporation, Sanechips |
| R2-2309915 | Discussion on RAN2 centric issues for LTM | CATT |
| R2-2309916 | Discussion on L1 related issues for LTM | CATT |
| R2-2309930 | Discussion on UE based TA measurement | Lenovo |
| R2-2309931 | Analysis on SCG LTM | Lenovo |
| R2-2310200 | LTM Configuration and Execution | MediaTek Inc. |
| R2-2310278 | Discussions on LTM related measurements | CMCC |
| R2-2310327 | RSTD based early TA acquisition | Apple |
| R2-2310339 | CFRA and CG configuration aspects in LTM | Apple |
| R2-2310371 | Discussion on RRC open issues for LTM | OPPO |
| R2-2310372 | Discussion on SCG LTM | OPPO |
| R2-2310398 | Remaining issue on LTM cell switch procedure | Fujitsu |
| R2-2310399 | L3 handover with LTM configuration | Fujitsu |
| R2-2310400 | Failure detection and fast recovery | Fujitsu |
| R2-2310440 | Prioritizing of LTM candidate cells | Rakuten Symphony |
| R2-2310473 | Security impacts of intra gNB, inter gNB-CU-UP relocation | Rakuten Symphony |
| R2-2310530 | Delayed Resource Reservation for inter gNB-DU LTM | Rakuten Symphony |
| R2-2310537 | TA acquisition related open issues | Rakuten Symphony |
| R2-2310538 | Miscellaneous issues of L1/L2 Triggered Mobility | Rakuten Symphony |
| R2-2310579 | Remaining issues of RRC configured Layer-2 reset | Xiaomi |
| R2-2310619 | Discussion on RRC aspects for L1/L2-Triggered Mobility | Xiaomi |
| R2-2310624 | Discussion on RRC aspects of LTM | Samsung |
| R2-2310633 | On Failure Handling for Rel-18 LTM | Nokia, Nokia Shanghai Bell |
| R2-2310634 | On SCG Release in Rel-18 LTM | Nokia, Nokia Shanghai Bell |
| R2-2310802 | Coexistence of LTM and L3M/CHO | Interdigital, Inc. |
| R2-2310803 | Fast RLF for LTM execution | Interdigital, Inc. |
| R2-2310887 | Discussion of remaining RRC open issues for LTM | Ericsson |
| R2-2310888 | Early sync and L1 measurements | Ericsson |
| R2-2310983 | Fast cell recovery aspects for LTM failures | Panasonic |
| R2-2310999 | RRC aspects for LTM | Huawei, HiSilicon |
| R2-2311091 | Conflict between LTM triggering and legacy RRC messaging | Qualcomm Incorporated |
| R2-2311095 | RRC aspects of LTM | Qualcomm Incorporated |
| R2-2311124 | Remaining issues for RRC Aspects of LTM | SHARP Corporation |
| R2-2311210 | LTM Cell Switch Aspects | Nokia, Nokia Shanghai Bell |
| R2-2311211 | On bearer handling in LTM | Nokia, Nokia Shanghai Bell |
| R2-2311283 | [AT123bis][505][feMob] LTM RRC | Ericsson |
| R2-2311332 | LS on CSI resource configuration and on early RACH for LTM | RAN2 |
| R2-2311333 | LS on L1 measurements for LTM | RAN2 |
| R2-2311533 | [DRAFT] LS on L1 measurements for LTM | Ericsson |
| R2-2311576 | LS on CSI resource configuration and on early RACH for LTM | Huawei |
| R2-2311604 | RRC running CR for LTM | Ericsson |
| R2-2311606 | RRC open issues list for LTM | Ericsson |
| 7.4.2.2 | L2 centric parts | |
| R2-2309546 | Discussion on L2 Centric Parts | CATT |
| R2-2309575 | Remaining aspects of Cell Switch | Lenovo |
| R2-2309582 | Remaining issues for RACH less LTM cell switch | NEC |
| R2-2309711 | Discussion on CFRA based LTM | LG Electronics |
| R2-2309712 | Discussion on L2 centric open issues | LG Electronics |
| R2-2309713 | Views on RACH-less fast recovery | KDDI Corporation |
| R2-2309721 | Contents of LTM MAC CE and other MAC related issue for LTM | vivo |
| R2-2309769 | Cell Switching – Open Issues | Samsung Electronics Co., Ltd |
| R2-2309770 | Early Timing Advance Management for LTM - Open Issues | Samsung Electronics Co., Ltd |
| R2-2309786 | Support UE based TA determination and RACH-less LTM | Futurewei |
| R2-2309788 | Lower layer operation for UE based RACH-less LTM | Futurewei |
| R2-2309851 | Support of UE-based TA acquisition for LTM | Samsung |
| R2-2309869 | 38.321 running CR for introduction of NR further mobility enhancements | Huawei, HiSilicon |
| R2-2309870 | Rapporteur proposals to address open issues in MAC running CRs (open issue list) | Huawei, HiSilicon |
| R2-2309871 | Early TA acquisition and LTM MAC CE format | Huawei, HiSilicon |
| R2-2309881 | Discussion on fallback RACH for L1L2-triggered mobility | ASUSTeK |
| R2-2309894 | RAN2 aspects of RACH-based early TA acquisition | Fujitsu |
| R2-2309895 | The completion of RACH-less LTM Cell switch | Fujitsu |
| R2-2309996 | Remaining issues to support PDCCH-ordered RACH for early TA acquisition | LG Electronics Inc. |
| R2-2310017 | Discussion on remaining issues of LTM cell switch procedure | Transsion Holdings |
| R2-2310018 | Discussion on remaining issues for LTM cell switch command | Transsion Holdings |
| R2-2310099 | Some views On Remaining L2 centric issues for LTM | ZTE Corporation, Sanechips |
| R2-2310100 | Further Discussion on RACH-less LTM | ZTE Corporation, Sanechips |
| R2-2310104 | Remaining issues on candidate cell TCI state activation | Panasonic |
| R2-2310277 | Discussions on LTM open issues | CMCC |
| R2-2310279 | Considerations on L2 centric parts | CMCC |
| R2-2310338 | On closing L2 centric open issues in LTM | Apple |
| R2-2310373 | Discussion on L2-centric issues for LTM | OPPO |
| R2-2310374 | Discussion on TCI state related issues for LTM | OPPO |
| R2-2310392 | RACH-Less LTM | MediaTek Inc. |
| R2-2310580 | RACH-less LTM and early TA | Xiaomi |
| R2-2310581 | Remaining issues for RACH-based LTM | Xiaomi |
| R2-2310646 | Discussion on L2 centric part of LTM | NEC |
| R2-2310739 | Discussions on TA acquisition and indication for Rach-less LTM | KDDI Corporation |
| R2-2310763 | RACH-less solution and TA indication for LTM | Sony |
| R2-2310804 | TA indication | Interdigital, Inc. |
| R2-2310889 | Remaining MAC issues | Ericsson |
| R2-2311001 | RACH-less LTM | Huawei, HiSilicon |
| R2-2311093 | Discussion on early TA acquisition and RACH-less LTM | Qualcomm Incorporated |
| R2-2311094 | L2 aspects of LTM | Qualcomm Incorporated |
| R2-2311105 | Discussion on LTM related MAC CE | NTT DOCOMO, INC. |
| R2-2311145 | Remaining issues for Early TA acquisition of RACH-less LTM | Sharp |
| R2-2311146 | Remaining issues for L2 centric parts of LTM | Sharp |
| R2-2311250 | Rapporteur proposals to address open issues in MAC running CRs (open issue list) | Huawei, HiSilicon |
| R2-2311574 | Summary of [AT123bis][514][feMob] LTM MAC Related Open Issues | Huawei, HiSilicon |
| R2-2311595 | 38.321 running CR for introduction of NR further mobility enhancements | Huawei, HiSilicon |
| 7.4.3 | Subsequent CPAC | |
| R2-2309547 | Discussion on subsequent CPAC | CATT |
| R2-2309722 | Remaining issues for subsequent CPAC | vivo |
| R2-2309831 | Summary of [Post123][054][feMob] Discussion on stage-2 signalling open issues | ZTE Corporation, Sanechips |
| R2-2309835 | Remaining issues on subsequent CPAC | ZTE Corporation, Sanechips |
| R2-2309852 | Considerations on Subsequent CPAC after SCG Change | Samsung |
| R2-2309908 | Discussion on Subsequent CPAC | FGI |
| R2-2309948 | Left issues on subsequent CPAC | Lenovo |
| R2-2310006 | Discussion on issues of subsequent CPAC | Spreadtrum Communications |
| R2-2310019 | Discussion on Selective Activation of Cell Groups in NR-DC | Transsion Holdings |
| R2-2310268 | Discussion on remaining open issues for subsequent CPAC | CMCC |
| R2-2310326 | Discussion on Subsequent CPAC | Apple |
| R2-2310337 | UE reporting of sk-counter for S-CPAC | Apple |
| R2-2310377 | Discussion on open issues for subsequent CPAC in NR-DC | OPPO |
| R2-2310529 | Subsequent CPAC in NR-DC | Qualcomm Incorporated |
| R2-2310573 | Discussion on the evaluation adjustment for SCPAC | ITRI |
| R2-2310620 | Discussion on subsequent CPAC | Xiaomi |
| R2-2310647 | Discussion on subsequent CPAC | NEC |
| R2-2310873 | Discussion on subsequent CPAC | MediaTek Inc. |
| R2-2310890 | Discussion on subsequent CPAC | Ericsson |
| R2-2310987 | Open issues regarding subsequent CPAC | Interdigital Inc. |
| R2-2311002 | Subsequent CPAC | Huawei, HiSilicon |
| R2-2311010 | Rapporteur summary Post[123][046][feMob] subsequent CPAC security issues | Nokia, Nokia Shanghai Bell |
| R2-2311011 | Discussion on Measurements, Reference Configuration, Security Issues, and Failure Handling for SCPAC | Nokia, Nokia Shanghai Bell |
| R2-2311096 | Stage 2 and 3 issues for Subsequent CPC | LG Electronics Inc. |
| R2-2311147 | Remaining issues for security aspects of Subsequent CPAC | Sharp |
| R2-2311148 | Discussion on subsequent CPAC | Sharp |
| R2-2311163 | Discussion on security issue for subsequent CPAC | NTT DOCOMO, INC. |
| R2-2311195 | Discussion on NR-DC with subsequent CPAC. | DENSO CORPORATION |
| R2-2311331 | LS on RAN2 progress on subsequent CPAC | RAN2 |
| R2-2311535 | [DRAFT] LS on RAN2 progress on subsequent CPAC | ZTE Corporation, Sanechips |
| R2-2311538 | Rapporteur summary [[AT123bis][503][feMob] subsequent CPAC security issues (Nokia) | Nokia, Nokia Shanghai Bell |
| R2-2311605 | RRC running CR for subsequent CPAC in NR-DC | OPPO |
| R2-2311607 | Reply LS on security for selective SCG activation | RAN2 |
| R2-2311618 | Reply LS on security for selective SCG activation | RAN2 |
| 7.4.4 | CHO including target MCG and candidate SCGs for CPC CPA in NR-DC | |
| R2-2309548 | Rapporteur proposals to open issues on CHO with candidate SCGs | CATT, Huawei, HiSilicon, MediaTek, vivo, Lenovo, OPPO, ZTE Corporation, Sanechips |
| R2-2309723 | Discussion on CHO with Candidate SCGs | vivo |
| R2-2309836 | Remaining issues on CHO with candidate SCG(s) | ZTE Corporation, Sanechips |
| R2-2309872 | Discussion on CHO with candidate SCG(s) | Huawei, HiSilicon |
| R2-2309907 | Discussion on CHO including target MCG and candidate SCGs | FGI |
| R2-2309932 | CHO with candidate SCG for CPAC | Lenovo |
| R2-2309981 | Considerations on CHO with CPA/CPC | Samsung |
| R2-2310020 | Discussion on CHO with candidate SCGs | Transsion Holdings |
| R2-2310224 | Discussion on open issues of CHO with candidate SCGs | China Telecom |
| R2-2310264 | Discussion on CHO with candidate SCGs | CMCC |
| R2-2310378 | Discussion on open issues for CHO with candidate SCGs | OPPO |
| R2-2310437 | Discussions on CHO with candidate SCGs | KDDI Corporation |
| R2-2310528 | CHO with multiple candidate SCGs | Qualcomm Incorporated |
| R2-2310621 | Discussion on CHO with candidate SCG(s) | Xiaomi |
| R2-2310635 | Final details on CHO with CPAC in Rel-18 | Nokia, Nokia Shanghai Bell |
| R2-2310891 | CHO with associated CPC or CPA | Ericsson |
| R2-2310988 | Open issues regarding CHO with associated SCG | Interdigital Inc. |
| R2-2311082 | On CHO recovery for CHO with candidate SCG | MediaTek Inc. |
| R2-2311097 | Simultaneous Execution of CHO and CPAC | LG Electronics Inc. |
| R2-2311249 | Rapporteur proposals to open issues on CHO with candidate SCGs | CATT, Huawei, HiSilicon, MediaTek, vivo, Lenovo, OPPO, ZTE Corporation, Sanechips, Nokia, Nokia Shanghai Bell |
| R2-2311532 | Report of [AT123bis][504][feMob] open issues on CHO with candidate SCGs (CATT) | CATT |
| R2-2311602 | RRC running CR for CHO with candidate SCG(s) | CATT |
| R2-2311603 | RRC Open issue list for CHO with candidate SCGs | CATT |
| 7.4.5 | Others | |
| R2-2309462 | LS on improvement on FR2 SCell/SCG setup delay (R4-2314466; contact: Nokia) | RAN4 |
| R2-2309545 | Discussion on improvement of FR2 SCell/SCG setup delay | CATT |
| R2-2310481 | Discussion on fast SCell/SCG setup | CMCC, Ericsson, ZTE, Huawei, vivo |
| R2-2310535 | Discussion on fast Scell setup | vivo |
| R2-2310796 | eEMR SCell setup delay | Nokia, Nokia Shanghai Bell |
| R2-2310801 | Improvement on Scell/SCG setup/resume delay | Interdigital, Inc. |
| R2-2310892 | Discussion on early measurements enhancements | Ericsson, CMCC |
| R2-2311078 | RAN2 signaling for improvement to SCellSCG setup delay | LG Electronics |
| R2-2311113 | Discussion on FR2 SCell/SCG setup delay | MediaTek Inc. |
| 7.5.1 | Organizational | |
| R2-2309431 | Reply LS on new DRX cycles in rational numbers (R1-2308654; contact: Qualcomm) | RAN1 |
| R2-2309432 | LS on stage 2 description for physical layer enhancements for XR (R1-2308659; contact: Nokia) | RAN1 |
| R2-2309455 | Reply LS on new DRX cycles in rational numbers (R4-2314383; contact: Niokia) | RAN4 |
| R2-2309480 | LS Reply on Design of RTP Header Extension for PDU Set Handling (S4-231592; contact: Lenovo) | SA4 |
| R2-2309724 | Running RLC CR for XR | vivo |
| R2-2309847 | Introduction of XR to PDCP | LG Electronics Inc. |
| R2-2309873 | Work Plan for Rel-18 WI on XR Enhancements for NR | Nokia, Qualcomm (Rapporteurs) |
| R2-2309874 | SA2 Status for XR | Nokia, Qualcomm (Rapporteurs) |
| R2-2309875 | SA4 Status for XR | Nokia, Qualcomm (Rapporteurs) |
| R2-2309876 | Stage 2 Overview of XR Enhancements | Nokia, Qualcomm (Rapporteurs) |
| R2-2309877 | XR Open Issues | Nokia, Huawei, Intel, LG, Qualcomm, Vivo (Rapporteurs) |
| R2-2310731 | Introduction of XR enhancements into TS 38.331 (running CR) | Huawei, HiSilicon |
| 7.5.2 | XR awareness | |
| R2-2309704 | Leftover issues on XR awareness | CATT |
| R2-2309725 | Discussion on XR awareness | vivo |
| R2-2309878 | RRC UAI and End of Data Burst for XR | Nokia, Nokia Shanghai Bell |
| R2-2309896 | Discussions on uplink End of Data Burst indication for XR | Fujitsu |
| R2-2309963 | Discussion on PDU sets and data burst awareness in RAN | Lenovo |
| R2-2309966 | Discussion on XR awareness | Samsung |
| R2-2310007 | Discussion on XR awareness | Spreadtrum Communications |
| R2-2310108 | Details of UAI for XR awareness in RAN | ZTE Corporation, Sanechips |
| R2-2310153 | UE Assistance on XR awareness support per QoS flow | Intel Corporation |
| R2-2310330 | Remaining Details of UAI for XR-Awareness | Apple |
| R2-2310386 | Discussion on XR awareness | OPPO |
| R2-2310432 | Remaining Issues of XR traffic assistance information | CMCC |
| R2-2310443 | End of data burst | LG Electronics Inc. |
| R2-2310452 | Remaing issues of XR awareness | NEC |
| R2-2310657 | Discussion on XR awareness | Xiaomi Communications |
| R2-2310664 | On XR awareness | Google Inc. |
| R2-2310729 | Discussion on XR assistance information for UL | Huawei, HiSilicon |
| R2-2310764 | Considerations on awareness of XR PDU prioritization | Sony |
| R2-2310786 | Remaining issues on XR awareness | China Telecom |
| R2-2310937 | XR awareness | InterDigital |
| R2-2311028 | Discussion on XR awareness | Ericsson |
| 7.5.3 | XR-specific power saving | |
| R2-2309486 | Power saving enhancements for XR | Qualcomm Incorporated |
| R2-2309640 | Remaining issues for C-DRX enhancements for XR | Huawei, HiSilicon |
| R2-2309692 | Remaining issues on DRX enhancement for XR | LG Electronics Inc. |
| R2-2309705 | Leftover issues on DRX enhancements | CATT |
| R2-2309726 | Analysis on remaining issues for C-DRX enhancements | vivo |
| R2-2309799 | Discussion on C-DRX enhancement for XR | NEC Corporation |
| R2-2309897 | Remaining issues on C-DRX enhancement for XR | Fujitsu |
| R2-2309964 | Discussion of DRX enhancement | Lenovo |
| R2-2309979 | Discussion on remaining issue of power saving scheme for XR | Samsung |
| R2-2310042 | Discussing on XR-specific power saving | Xiaomi Communications |
| R2-2310110 | XR-specific power saving | ZTE Corporation, Sanechips |
| R2-2310255 | Discussion on the DRX enhancement | CMCC |
| R2-2310387 | Discussion on XR-specific power saving | OPPO |
| R2-2310477 | Discussion on various frame rates supported for XR-specific power | III |
| R2-2310666 | XR-specific power saving enhancement | Google Inc. |
| R2-2310686 | DRX enhancements for XR | Nokia, Nokia Shanghai Bell |
| R2-2310787 | Discussion on DRX enhancements for XR | China Telecom Corporation Ltd. |
| R2-2310929 | Remaining issues for C-DRX in XR | MediaTek Inc |
| R2-2311029 | Discussion on XR-specific power saving | Ericsson |
| 7.5.4.1 | BSR enhancements for XR | |
| R2-2309487 | BSR enhancements for XR | Qualcomm Incorporated |
| R2-2309488 | Delay status reporting for XR | Qualcomm Incorporated |
| R2-2309593 | Discussion on Delay status report | CANON Research Centre France |
| R2-2309594 | Detailed Buffer Size table design for XR | Futurewei |
| R2-2309595 | Detailed DSR MAC CE design for XR | Futurewei |
| R2-2309706 | Consideration on DSR and BSR | CATT |
| R2-2309727 | Discussion on BSR enhancements for XR | vivo |
| R2-2309728 | Discussion on DSR for XR | vivo |
| R2-2309800 | Discussion on delay status reporting for XR | NEC Corporation |
| R2-2309898 | Discussions on delay information reporting | Fujitsu |
| R2-2309910 | Discussion on delay status reporting for XR | FGI |
| R2-2309965 | Discussion on BSR enhancements for XR | Lenovo |
| R2-2310047 | Discussing on BSR enhancements for XR capacity | Xiaomi Communications |
| R2-2310068 | Discussion on BSR and DSR enhancements for XR | Honor |
| R2-2310109 | BSR enhancements for XR | ZTE Corporation, Sanechips |
| R2-2310140 | Delay status reporting for XR | Lenovo |
| R2-2310152 | New BSR trigger due to UE’s discard operation | Intel Corporation |
| R2-2310238 | Discussion on Rel-18 XR-specified remaining time and BSR table | CMCC |
| R2-2310331 | BSR Enhancemenrts for XR | Apple |
| R2-2310332 | Delay Status Reporting for XR | Apple |
| R2-2310388 | Discussion on BSR enhancement for XR | OPPO |
| R2-2310470 | Discussion on BSR enhancements for XR | III |
| R2-2310536 | Discussion on DSR enhancements for XR | Huawei, HiSilicon |
| R2-2310601 | Discussion on BSR enhancement with new BS Table | LG Electronics Inc. |
| R2-2310602 | Discussion on delay status report | LG Electronics Inc. |
| R2-2310659 | Details of the New BS table | NEC |
| R2-2310683 | Discussion on delay status report for XR | Google Inc. |
| R2-2310687 | BSR enhancements for XR | Nokia, Nokia Shanghai Bell |
| R2-2310765 | Some considerations on BSR enhancements for XR | Sony |
| R2-2310788 | Remaining issues on delay status reporting | China Telecom Corporation Ltd. |
| R2-2310944 | DSR for XR | MediaTek Inc |
| R2-2310989 | Buffer status reporting for XR | Interdigital Inc. |
| R2-2310990 | Remaining time reporting for XR | Interdigital Inc. |
| R2-2311030 | Discussion on BSR enhancements for XR | Ericsson |
| R2-2311073 | Discussion on BSR enhancements for XR | Samsung |
| R2-2311104 | Discussion on delay status reporting for XR | DENSO CORPORATION |
| R2-2311139 | Discussion on DSR | TCL |
| 7.5.4.2 | Discard operation for XR | |
| R2-2309489 | A PDU discard procedure based on buffer threshold | Qualcomm Incorporated |
| R2-2309707 | PDCP discard notifications to receiving PDCP entity | CATT, CANON Research Centre France |
| R2-2309708 | Leftover Issues on Discard | CATT |
| R2-2309729 | Discussion on discard operation for XR | vivo |
| R2-2309848 | PSI based PDCP discard mechanism | LG Electronics, CATT, Vivo, Fujitsu, III, Samsung, LG Uplus, ZTE, KDDI, Google, Intel Corporation |
| R2-2309879 | Discard Operation for XR | Nokia, Nokia Shanghai Bell |
| R2-2309899 | Discussions on PDU discard based on PDU Set Importance | Fujitsu |
| R2-2310008 | Discussion on XR discard operation | Spreadtrum Communications |
| R2-2310043 | Discussing on PDU discarding of XR traffic | Xiaomi Communications |
| R2-2310045 | Discussing on PDU discarding of XR traffic | Xiaomi Communications |
| R2-2310089 | Discard Operation for XR | Samsung R&D Institute India |
| R2-2310111 | PDU discard for XR | ZTE Corporation, Sanechips |
| R2-2310141 | PSI based discarding operation for XR | Lenovo |
| R2-2310151 | Support of discard at lower layers | Intel Corporation |
| R2-2310175 | Discussion on PDU Discard Operation for XR | Meta |
| R2-2310333 | Views on Threshold Signaling for PSI-based Discarding Mechanism | Apple, Huawei, HiSilicon, ITRI, Lenovo, NTT Docomo, Qualcomm |
| R2-2310389 | Discussion on discard operation for XR | OPPO |
| R2-2310433 | Buffer Size Threshold-based Discard for XR | CMCC |
| R2-2310534 | Discussion on Timer-based PDU set discarding for XR traffic | Huawei, HiSilicon, Spreadtrum Communications, Apple, Lenovo, OPPO, Canon, NTT DOCOMO INC., ITRI, NEC, InterDigital |
| R2-2310576 | UL PSI Values, Discard and Thresholds vs Timers | Vodafone GmbH |
| R2-2310660 | An updated Timer-based Solution | NEC |
| R2-2310681 | Discussion on PSI-based discard for XR | Google Inc. |
| R2-2310766 | Discard timer-based PSI discard | Sony |
| R2-2310922 | On PSI and discard | MediaTek Inc |
| R2-2310938 | Discard operation for XR | InterDigital |
| R2-2311027 | Discussion on PSI-based discarding | Ericsson |
| R2-2311138 | Discussion on PSI-based uplink discard | TCL |
| R2-2311141 | Remaining issues in PSI-based SDU discarding | Futurewei |
| R2-2311142 | Implications of PDU Set discarding and potential solutions | Futurewei |
| 7.5.4.3 | Configured Grant enhancements for XR | |
| R2-2309490 | Configured grant enhancements for XR | Qualcomm Incorporated |
| R2-2309523 | Configured Grant enhancements for XR | Xiaomi |
| R2-2309642 | Discussion on Multi-PUSCH CG | Huawei, HiSilicon |
| R2-2309709 | Leftover issues on configured grant | CATT |
| R2-2309900 | Discussions on unused CG PUSCH transmission occasions | Fujitsu |
| R2-2309967 | Discussion on CG enhancements | Samsung |
| R2-2310112 | Configured Grant enhancements for XR | ZTE Corporation, Sanechips |
| R2-2310142 | CG enhancements for XR communications | Lenovo |
| R2-2310239 | Discussion on Rel-18 XR-specified CG enhancement | CMCC |
| R2-2310334 | UTO for Multi-PUSCH Configured Grant | Apple |
| R2-2310390 | Discussion on configured grant enhancement for XR | OPPO |
| R2-2310471 | Discussion on Configured Grant enhancements for XR | III |
| R2-2310603 | Discussion on CG enhancement for XR | LG Electronics Inc. |
| R2-2310661 | CG Enhancement for XR | NEC |
| R2-2310665 | On Configured Grant enhancements for XR | Google Inc. |
| R2-2310688 | CG enhancements for XR | Nokia, Nokia Shanghai Bell |
| R2-2310767 | Configured Grant enhancements for XR | Sony |
| R2-2310939 | Configured Grant enhancements for XR | InterDigital |
| R2-2311137 | Discussion on multiple-PUSCHs CG | TCL |
| R2-2311246 | Configured Grant enhancements for XR | Ericsson |
| 7.5.5 | UE capabilities for XR | |
| R2-2309491 | UE capabilities for XR services | Qualcomm Incorporated |
| R2-2309524 | UE capabilities for XR | Xiaomi |
| R2-2309730 | Discussion on UE capability for XR | vivo |
| R2-2309880 | UE capabilities for Rel-18 XR | Nokia, Nokia Shanghai Bell |
| R2-2309968 | UE capability for XR | Samsung |
| R2-2310113 | UE capabilities for XR | ZTE Corporation, Sanechips |
| R2-2310148 | Summary on UE Capabilities for Rel-18 XR WI | Intel Corporation, Qualcomm Incorporated, Xiaomi, InterDigital, Nokia, Nokia Shanghai Bell, vivo, OPPO, Huawei, HiSilicon, Ericsson |
| R2-2310149 | UE Capabilities for Rel-18 XR WI | Intel Corporation |
| R2-2310150 | UE Capabilities for Rel-18 XR WI | Intel Corporation |
| R2-2310335 | UE Capabilities for XR | Apple |
| R2-2310391 | Discussion on UE capabilities for XR | OPPO |
| R2-2310730 | Discussion on UE capabilities for XR | Huawei, HiSilicon |
| R2-2311031 | Discussion on UE capabilities for XR | Ericsson |
| R2-2311111 | UE Capabilities for Rel-18 XR | Meta |
| R2-2311587 | [Draft] LS on XR awareness | vivo |
| R2-2311590 | LS on XR awareness | RAN2 |
| 7.6.1 | Organizational | |
| R2-2309416 | LS on Rel-18 RAN1 UE features list for LTE after RAN1#114 (R1-2308520; contact: NTT DOCOMO, AT&T) | RAN1 |
| R2-2309532 | Discussion on R18 IoT NTN UE capabilities | OPPO |
| R2-2310180 | Running CR for TS 36.306 for Rel-18 IoT NTN | Qualcomm Incorporated |
| R2-2310410 | 36331 running CR for IOT NTN | Huawei, HiSilicon |
| R2-2311070 | Stage-3 running CR for TS 36.321 for Rel-18 IoT-NTN | MediaTek Inc. |
| R2-2311194 | 36304 Running CR for IoT-NTN | Nokia Solutions & Networks (I) |
| R2-2311244 | Introduction of IoT NTN enhancements | Ericsson |
| R2-2311245 | Rapporteur input on 36.300 | Ericsson |
| 7.6.2.1 | HARQ enhancements | |
| R2-2309527 | Discussion on HARQ enhancement for IoT NTN | OPPO |
| R2-2309657 | Remaining Issues on HARQ Enhancement for IoT NTN | vivo |
| R2-2309701 | Remaining issues of HARQ enhancement | Huawei, Turkcell, HiSilicon |
| R2-2309752 | Discussion on HARQ enhancements in IoT NTN | CATT |
| R2-2309758 | Discussion on HARQ enhancement | Xiaomi |
| R2-2309781 | On Disabling HARQ Feedback in IoT-NTN | MediaTek Inc. |
| R2-2309956 | Views on some remaining issues for HARQ in IoT NTN | Lenovo |
| R2-2310181 | DCI-based HARQ feedback overriding solution | Qualcomm Incorporated |
| R2-2310269 | Discussion on the HARQ enhancement for IoT-NTN | CMCC |
| R2-2310651 | Further discussion on HARQ enhancements for IoT NTN | Nokia, Nokia Shanghai Bell |
| R2-2310805 | Disabling HARQ feedback for IoT-NTN | Interdigital, Inc. |
| R2-2310820 | Remaining issues of HARQ enhancements | ZTE Corporation, Sanechips |
| R2-2311243 | R18 IoT NTN HARQ enhancements | Ericsson |
| R2-2311320 | Summary of [AT123bis][308][IoT-NTN Enh] HARQ enhancements (OPPO) | OPPO |
| 7.6.2.2 | GNSS operation enhancements | |
| R2-2309531 | Discussion on GNSS operation for IoT NTN | OPPO |
| R2-2309658 | Discussion on GNSS Operation for IoT NTN | vivo |
| R2-2309702 | Discussion on the impact of GNSS measurement | Huawei, Turkcell, HiSilicon |
| R2-2309751 | Discussion on GNSS operation enhancements | CATT |
| R2-2309757 | Discussion on GNSS operation enhancement | Xiaomi |
| R2-2309782 | Enhancements on GNSS operation | MediaTek Inc. |
| R2-2309957 | Views on some remaining issues for GNSS operations in IoT NTN | Lenovo |
| R2-2309997 | Remaining issues on the GNSS operation | Google Inc. |
| R2-2310184 | GNSS fix in RRC_CONNECTED | Qualcomm Incorporated |
| R2-2310270 | Discussion on GNSS enhancement for IoT-NTN | CMCC |
| R2-2310323 | Concluding critical issues in improved GNSS operation | Apple |
| R2-2310650 | GNSS Validity duration Reporting | Nordic Semiconductor ASA |
| R2-2310652 | Further discussion on GNSS operation enhancement in Rel-18 IoT NTN | Nokia, Nokia Shanghai Bell |
| R2-2310806 | GNSS acquisition and reporting for IoT NTN | Interdigital, Inc. |
| R2-2310821 | Remaining issues of GNSS enhancements | ZTE Corporation, Sanechips |
| R2-2311036 | On improved GNSS operation for IoT NTN | Samsung Electronics Polska |
| R2-2311086 | Discussion of GNSS operation enhancements | SHARP Corporation |
| R2-2311242 | R18 IoT NTN GNSS operation enhancements | Ericsson |
| R2-2311258 | GNSS Validity duration Reporting | Nordic Semiconductor ASA |
| R2-2311321 | Summary of [AT123bis][309][IoT-NTN Enh] GNSS Enhancements (Mediatek) | Mediatek |
| 7.6.3 | Mobility Enhancements | |
| R2-2309958 | Views on some remaining issues for mobility in IoT NTN | Lenovo |
| 7.6.3.1 | Enhancements for neighbour cell measurements | |
| R2-2309528 | Discussion on mobility enhancement for IoT NTN | OPPO |
| R2-2309762 | Discussion on UE behavior when serving cell t-service expires | Xiaomi |
| R2-2309783 | Enhancements on neighbor cell measurement | MediaTek Inc. |
| R2-2310183 | Measurement and Mobility enhancements | Qualcomm Incorporated |
| R2-2310271 | Discussion on mobility enhancements for IoT-NTN | CMCC |
| R2-2310324 | Neighbour cell measurements before RLF for eMTC-NTN | Apple, MediaTek Inc. |
| R2-2310411 | Remaining issues on mobility enhancements | Huawei, HiSilicon, Turkcell |
| R2-2310628 | On enhancements for neighbour cell measurements | Samsung Electronics Polska |
| R2-2310807 | Fast RLF and re-establishment in the discontinuous coverage scenario | Interdigital, Inc. |
| R2-2310822 | Remaining issues of mobility enhancements | ZTE Corporation, Sanechips |
| R2-2311012 | On Remaining issues for IoT-NTN Mobility Enhancements | Nokia, Nokia Shanghai Bell |
| R2-2311069 | Discussion on gaps for neighbour cell measurements in IoT NTN | Ericsson |
| R2-2311240 | Discussion on triggering RA for RRC connection re-establishment in IoT NTN | Ericsson |
| 7.6.3.2 | Other | |
| R2-2309659 | Discussion on CHO Enhancement for IoT NTN | vivo |
| R2-2310192 | NB-IoT NTN Coarse UE location reporting | Inmarsat, Viasat, Sateliot, Novamint, ESA, Thales |
| R2-2310325 | Mobility enhancement in IoT NTN | Apple |
| R2-2310629 | On other mobility enhancements for IoT NTN | Samsung Electronics Polska |
| R2-2311322 | LS on UE Location Information for NB-IoT NTN | RAN2 |
| R2-2311325 | LS on UE Location Information for NB-IoT NTN | RAN2 |
| R2-2311326 | LS on UE Location Information for NB-IoT NTN | RAN2 |
| 7.6.4 | Enhancements to discontinuous coverage | |
| R2-2309660 | Discussion on Discontinuous Coverage | vivo |
| R2-2309703 | Remaining issues of discontinuous coverage | Huawei, Turkcell, HiSilicon |
| R2-2309753 | Discussion on discontinuous coverage enhancement | CATT |
| R2-2309882 | Discussion on TN coverage for discontinuous coverage | ASUSTeK |
| R2-2309959 | Views on some remaining issues for discontinuous coverage in IoT NTN | Lenovo |
| R2-2310021 | Discussion on enhancement to discontinuous coverage for IoT NTN | Transsion Holdings |
| R2-2310071 | Considerations on Supporting Discontinuous Coverage | NEC |
| R2-2310182 | RRC release procedure in discontinuous coverage | Qualcomm Incorporated |
| R2-2310808 | RRC Release in discontinuous coverage | Interdigital, Inc. |
| R2-2310826 | Remaining issues of discontinuous coverage | ZTE Corporation, Sanechips |
| R2-2310919 | Enhancements to discontinuous coverage | Samsung Electronics Iberia SA |
| R2-2311013 | Discussion on discontinuous coverage Enhancements | Nokia, Nokia Shanghai Bell |
| R2-2311232 | Measurement information to assist cell search after a coverage gap | Ericsson |
| 7.7.1 | Organizational | |
| R2-2309407 | LS on the service requirement of restricting satellite access RAT type (C1-236567; contact: Google) | CT1 |
| R2-2309421 | Reply LS to RAN2 on unchanged PCI (R1-2308566; contact: CATT) | RAN1 |
| R2-2309422 | Reply LS on RACH-less Handover (R1-2308568; contact: Samsung) | RAN1 |
| R2-2309438 | Reply LS on Common Signaling in (C)HO (R3-234664; contact: Qualcomm) | RAN3 |
| R2-2309476 | Reply LS on time-based trigger condition in NG HO for NR NTN (S2-2310013; contact: Samsung) | SA2 |
| R2-2310084 | Remaining Issues on NR Non-Terrestrial Networks (NTN) | THALES |
| R2-2310085 | R18 WI NR-NTN-enh work plan at RAN1, 2 and 3 | THALES |
| R2-2310157 | UE Capabilities for Rel-18 NR NTN Enh. WI | Intel Corporation |
| R2-2310158 | UE Capabilities for Rel-18 NR NTN Enh. WI | Intel Corporation |
| R2-2310552 | Stage 3 running 38.304 CR for NTN | ZTE Corporation, Sanechips |
| R2-2310840 | Stage 3 NTN running CR for 38.321 - RAN2#123 | InterDigital |
| R2-2310841 | MAC open issues in NTN | InterDigital |
| R2-2311230 | Stage 3 Running RRC CR for NR NTN Rel-18 | Ericsson |
| R2-2311231 | Rapporteur s input to 38.331 regarding TN area information | Ericsson |
| R2-2311255 | Stage-2 running CR for TS 38.300 for Rel-18 NTN enhancements | THALES (Rapporteur) |
| 7.7.2 | Coverage Enhancements | |
| R2-2309529 | Discussion on PUCCH enhancement for Msg4 HARQ-ACK in NR NTN | OPPO |
| R2-2310000 | Higher layer signalling for PUCCH repetition for Msg4 HARQ-ACK | Huawei, HiSilicon |
| R2-2310559 | Consideration on coverage enhancements | ZTE Corporation, Sanechips |
| 7.7.3 | Network verified UE location | |
| R2-2309503 | Remaining issues on NW verification of UE location in R18 NR NTN | CATT |
| R2-2309700 | Handling of UE location verification during handover | Huawei, Turkcell, HiSilicon |
| R2-2309989 | Views on some remaining issues for network verified UE location | Lenovo Information Technology |
| R2-2309990 | Discussion on Network Verified UE Location | TCL |
| R2-2309995 | Multiple-RTT positioning in NTN | Quectel |
| R2-2310037 | Discussion on network verified UE location in NR NTN | THALES |
| R2-2310133 | Discussion on network verified UE location | Ericsson |
| R2-2310147 | Open issues on Network verified location | Nokia, Nokia Shanghai Bell |
| R2-2310176 | Single satellite Multi-RTT based positioning | Qualcomm Incorporated |
| R2-2310245 | Discussion on the remaining issues for network verified UE location | CMCC |
| R2-2310418 | Discussion on network verified UE location | Xiaomi |
| R2-2310560 | Consideration on NW verified UE location | ZTE Corporation, Sanechips |
| R2-2310985 | UE location verification by Network | NEC Telecom MODUS Ltd. |
| R2-2311009 | Network Verified UE Location in NTN | Samsung Electronics Iberia SA |
| R2-2311316 | Report of [304][NR-NTN Enh] NW verified UE location failure during cell change | Qualcomm Incorporated |
| R2-2311323 | Draft LS on NW verified UE location failure during cell change | Qualcomm Incorporated |
| R2-2311324 | LS on NW verified UE location failure during cell change | RAN2 |
| 7.7.4.1 | Cell reselection enhancements | |
| R2-2310046 | Discussion on mobility enhancements for VSAT | THALES |
| R2-2310246 | Discussion on left issues for cell reselection | CMCC |
| 7.7.4.1.1 | NTN-TN enhancements | |
| R2-2309653 | Remaining Issues on Cell Reselection for Power Saving | vivo |
| R2-2309862 | Remaining issues on NTN-TN cell reselection enhancement | LG Electronics France |
| R2-2309909 | Discussion on TN Coverage Area Information Update Issues | FGI |
| R2-2309960 | Views on some remaining issues for NTN-TN mobility | Lenovo |
| R2-2310065 | Open issues of cell reselection enhancement | Samsung Research America |
| R2-2310177 | TN cell coverage info and measurement relaxation | Qualcomm Incorporated |
| R2-2310306 | NTN-TN cell reselection enhancement | Apple |
| R2-2310419 | Cell reselection enhancements for NTN-TN mobility | Xiaomi |
| R2-2310626 | Discussion on TN Measurement Relaxation Issues | FGI |
| R2-2310842 | NTN-TN mobility and service continuity | InterDigital |
| R2-2310986 | On the use of TN coverage signalling to indicate non-TN areas | NEC Telecom MODUS Ltd. |
| R2-2311229 | NTN neighbour cell information in TN cells | Ericsson, Thales |
| R2-2311317 | Report of [AT123bis][305][NR-NTN Enh] Support of NTN neighbor cell info | Ericsson |
| 7.7.4.1.2 | NTN-NTN enhancements | |
| R2-2310413 | Discussion on location-based measurement initiation in moving cells | Huawei, HiSilicon, Turkcell |
| R2-2310843 | Cell reselection enhancements for Earth moving cell | InterDigital |
| R2-2311228 | Cell reselection enhancements | Ericsson |
| 7.7.4.2 | Handover enhancements | |
| R2-2309500 | Discussion on common (C)HO configuration | CATT |
| R2-2309501 | Discussion on RACH-less HO in NR NTN | CATT |
| R2-2309502 | Discussion on unchanged PCI mechanism | CATT |
| R2-2309537 | Discussion on handover enhancement for NR NTN | OPPO |
| R2-2309654 | Further Discussion on CHO Enhancements for NR NTN | vivo |
| R2-2309655 | Remaining Issue on RACH-less for R18 NR NTN | vivo |
| R2-2309656 | Further Discussion on Service Link Switching with Unchanged PCI | vivo |
| R2-2309784 | Handover Enhancement in LEO NTN: Unchanged PCI | MediaTek Inc. |
| R2-2309863 | Remaining issues on handover enhancements | LG Electronics France |
| R2-2309864 | Discussion on unchanged PCI | TCL |
| R2-2309865 | Discussion on RACH-less HO | TCL |
| R2-2309883 | Discussion on moving cell reference location for CHO | ASUSTeK |
| R2-2309884 | Discussion on remaining issue for unchanged PCI switch | ASUSTeK |
| R2-2309961 | Views on some remaining issues for PCI-unchanged scenario | Lenovo |
| R2-2309962 | Views on some remaining issues for RACH-less HO in NTN | Lenovo |
| R2-2310022 | Discussion on remaining issues of PCI unchanged handover | Transsion Holdings |
| R2-2310034 | Discussion on satellite switch with longer gap in conjunction with unchanged PCI | PANASONIC R&D Center Germany |
| R2-2310066 | CHO Enhancements for NTN | Samsung Research America |
| R2-2310067 | Open issues on NTN RACH-less HO and PCI unchanged switch | Samsung Research America |
| R2-2310178 | RACH-less handover for NTN | Qualcomm Incorporated |
| R2-2310179 | Details on satellite switch with PCI unchange | Qualcomm Incorporated |
| R2-2310225 | Aquisition of target satellite information with PCI unchanged | China Telecom |
| R2-2310247 | Further discussion on PCI unchanged | CMCC |
| R2-2310307 | Satellite switching with unchanged PCI | Apple |
| R2-2310308 | NR NTN specific HO enhancement | Apple |
| R2-2310412 | Discussion on handover enhancements | Huawei, HiSilicon, Turkcell |
| R2-2310420 | Discussion on handover enhancements for NTN-NTN mobility | Xiaomi |
| R2-2310435 | Remaining issue on RACH-less HO for NTN | ITL |
| R2-2310561 | Consideration on remaining issues on NTN HO enhancements | ZTE Corporation, Sanechips |
| R2-2310636 | On Common HO Signalling for Rel-18 NTN | Nokia, Nokia Shanghai Bell |
| R2-2310637 | Final View on RACH-less HO in Rel-18 NTN | Nokia, Nokia Shanghai Bell |
| R2-2310638 | On How To Resolve Remaining Issues for Unchanged PCI (Satellite Switching without L3 Mobility) | Nokia, Nokia Shanghai Bell |
| R2-2310662 | Remaining Issues of RACH-less (C)HO | NEC |
| R2-2310663 | Remaining Details of Unchanged PCI Switch | NEC |
| R2-2310696 | Remaining issues on the unchanged PCI satellite switch | Google Inc. |
| R2-2310697 | Discussion on the unchanged PCI scenario with optional random access | ETRI |
| R2-2310768 | Common handover signalling for NTN | Sony |
| R2-2310769 | Signaling overhead reduction during NTN-NTN HOs | Sony |
| R2-2310844 | NTN mobility enhancements for RRC_CONNECTED | InterDigital |
| R2-2310845 | Satellite switching without PCI change | InterDigital |
| R2-2311019 | Remaining issues on RACH-less HO for NR NTN | ETRI |
| R2-2311144 | Discussion on NTN HO enhancements | Sharp |
| R2-2311212 | Common signalling of HO common information | Sequans Communications |
| R2-2311223 | “Unchanged PCI” solution vs “PCI change only” solution | Sequans Communications |
| R2-2311227 | Handover enhancements | Ericsson |
| R2-2311318 | [AT123bis][306][NR-NTN Enh] RACH-less HO | InterDigital |
| R2-2311319 | [AT123bis][307][NR-NTN Enh] Unchanged PCI (Apple) | Apple |
| 7.8.1 | Organizational | |
| R2-2309467 | LS on the handling of additional regulatory requirements for UAV UEs (R4-2314700; contact: Ericsson) | RAN4 |
| R2-2309611 | RRC Running CR (Introduction of Aerial Support) | Qualcomm Incorporated |
| R2-2310639 | Uncrewed Aerial Vehicles in Rel-18 - Updated Workplan | Nokia, Nokia Shanghai Bell |
| R2-2310640 | 38.300 Running CR for Rel-18 UAVs | Nokia, Nokia Shanghai Bell |
| R2-2310641 | 36.300 Running CR for Rel-18 UAVs | Nokia, Nokia Shanghai Bell |
| R2-2310642 | On NS Value Signalling for Rel-18 UAVs | Nokia, Nokia Shanghai Bell |
| R2-2310643 | On UE Capabilities for Rel-18 UAVs | Nokia, Nokia Shanghai Bell |
| R2-2310935 | Discussion on UE capabilities for UAV | Huawei, HiSilicon |
| R2-2310936 | Introduction of capabilities for Rel-18 NR Support for UAV WI | Huawei, HiSilicon |
| R2-2310942 | Introduction of capabilities for Rel-18 Enhanced LTE Support for UAV WI | Huawei, HiSilicon |
| R2-2310943 | Introduction of capabilities for Rel-18 Enhanced LTE Support for UAV WI | Huawei, HiSilicon |
| R2-2310973 | Discussion on and DRAFT reply to the RAN4 LS on the handling of additional regulatory requirements for UAV UEs | Qualcomm Incorporated |
| R2-2311170 | Signalling of NS values for Aerial UEs | Ericsson |
| R2-2311287 | Reply LS on the handling of additional regulatory requirements for UAV Ues | RAN2 |
| 7.8.2 | Measurement reporting for mobility and interference control | |
| R2-2309936 | Remaining issue on height dependent measurement for NR UAV | Lenovo |
| R2-2309937 | Discussion on no-transmit zone for UAV UE | Lenovo |
| R2-2310069 | Remaining Issues on Measurement Reports Enhancements | NEC |
| R2-2310248 | [Draft] LS to RAN1 on UL power control for NR UAV | CMCC |
| R2-2310249 | Considerations on measurement reporting | CMCC |
| R2-2310328 | Measurement reporting enhancement in UAV | Apple |
| R2-2310461 | Proposed resolutions for Editor’s Notes and FFSes in the RRC running CR | Qualcomm Incorporated |
| R2-2310462 | Altitude-dependent SSB-ToMeasure for RRC_IDLE/RRC_INACTIVE mode measurements | Qualcomm Incorporated |
| R2-2310531 | Discussion on measurement reporting enhancement for NR UAV | vivo |
| R2-2310532 | Discussion on Height-dependent measurement configuration enhancement for NR UAV | vivo |
| R2-2310548 | Measurement reporting based on height-dependent configuration | Sharp |
| R2-2310607 | On height-dependent SSB-ToMeasure configuration | ZTE Corporation, Sanechips |
| R2-2310608 | On measurement reporting enhancement | ZTE Corporation, Sanechips |
| R2-2310622 | Discussion on measurement reporting enhancements for NR UAV | Xiaomi |
| R2-2310790 | Discussion on measurement reporting | China Telecom Corporation Ltd. |
| R2-2310931 | Measurement report enhancement for NR UAV | Huawei, HiSilicon |
| R2-2311055 | On UAV Measurement Reporting Behaviour | Nokia, Nokia Shanghai Bell |
| R2-2311074 | Remaining issues on measurement reporting enhancements in NR UAV | Samsung |
| R2-2311102 | Measurement Report Enhancement | LG Electronics |
| R2-2311154 | Prohibit timer for mobility measurement reporting for UAVs | Ericsson, Intel, Docomo, China Telecom, Denso |
| 7.8.3 | Flight path reporting | |
| R2-2309921 | Discussion on flight path reporting | Samsung |
| R2-2310070 | Remaining Issues on Flight Path Reporting | NEC |
| R2-2310250 | Discussion on flight path reporting | CMCC |
| R2-2310533 | Discussion on the remaining issue on flight path reporting | vivo |
| R2-2310609 | On flight path reporting | ZTE Corporation, Sanechips |
| R2-2310623 | Discussion on flight path reporting for NR UAV | Xiaomi |
| R2-2310791 | Discussion on flight path reporting | China Telecom Corporation Ltd. |
| R2-2310846 | Flightpath update notification for UAV | InterDigital |
| R2-2310923 | UAV Flight Path Reporting | Ericsson España S.A. |
| R2-2310933 | Further discussion on flight path reporting | Huawei, HiSilicon |
| R2-2311103 | Consideration on flight path reporting for NR UAV | DENSO CORPORATION |
| 7.8.5 | UAV identification broadcast | |
| R2-2309938 | Discussion on broadcasting remote id for UAV | Lenovo |
| R2-2309969 | SL configuration for BRID and DAA | Samsung |
| R2-2310251 | Considerations on left issues for UAV identification broadcast | CMCC |
| R2-2310472 | Remaining aspects of PC5-based BRID and DAA support | Qualcomm Incorporated |
| R2-2310924 | UAV Broadcast Identification | Ericsson España S.A. |
| R2-2310934 | Further discussion on UAV remote identification broadcast | Huawei, HiSilicon |
| R2-2311157 | UAV remote ID and related items | Beijing Xiaomi Mobile Software |
| 7.9.1 | Organizational | |
| R2-2309683 | Running CR of TS 38.351 for SL Relay enhancement | OPPO |
| R2-2309755 | Report of [Post123][Relay] Remaining open issues (LG) | LG Electronics France |
| R2-2309911 | Introduction of Rel-18 SL relay service continuity | MediaTek Inc |
| R2-2310166 | Draft 38.323 running CR for enhanced NR sidelink relay | InterDigital |
| R2-2310359 | Running CR of TS 38.321 for SL Relay enhancement | Apple |
| R2-2310484 | RRC running CR for Rel-18 multi-path support | Huawei, HiSilicon |
| R2-2310485 | RRC open issues for Rel-18 Multi-path | Huawei, HiSilicon |
| R2-2311025 | Introduction of Rel-18 support for SL Relay Enhancements | Ericsson España S.A. |
| R2-2311256 | Introduction of Rel-18 support for SL Relay Enhancements | Ericsson España S.A. |
| R2-2311264 | Introduction of NR sidelink U2U relay | vivo |
| R2-2311556 | Running CR of TS 38.351 for SL Relay enhancement | OPPO |
| R2-2311557 | Introduction of Rel-18 SL relay service continuity | MediaTek Inc |
| R2-2311558 | Draft 38.323 running CR for enhanced NR sidelink relay | InterDigital |
| R2-2311559 | Running CR of TS 38.321 for SL Relay enhancement | Apple |
| R2-2311560 | RRC running CR for Rel-18 multi-path support | Huawei, HiSilicon |
| R2-2311561 | Introduction of Rel-18 support for SL Relay Enhancements | Ericsson España S.A. |
| R2-2311562 | Introduction of NR sidelink U2U relay | vivo |
| 7.9.2 | UE-to-UE relay | |
| R2-2309612 | Discussion on U2U Relay | CATT |
| R2-2309613 | Cross Group Issue for U2U Relay | CATT |
| R2-2309679 | Discussion on control plane procedure of U2U relay | OPPO |
| R2-2309680 | Discussion on user plane procedure of U2U relay | OPPO |
| R2-2309817 | Discussion on CP aspects for U2U relay | Xiaomi |
| R2-2309822 | Remaining issues on U2U relay | vivo |
| R2-2309885 | Remaining issues on AS layer configuration for L2 U2U Relay | ASUSTeK |
| R2-2309886 | Remaining issues on PC5 radio link failure and PC5 link release | ASUSTeK |
| R2-2309887 | Remaining issue on E2E PC5-RRC procedures | ASUSTeK |
| R2-2309901 | Discussion on U2U relay | Fujitsu |
| R2-2309905 | Summary of [Post123][406][Relay] Local ID in SRAP (OPPO) | OPPO |
| R2-2309927 | Discussion on L2 U2U relay | Lenovo |
| R2-2309970 | Control plane issues for L2 U2U relay | Samsung |
| R2-2309975 | Discussion on U2U Relay discovery and (re)selection | ZTE, Sanechips |
| R2-2309976 | Discussion on U2U relay L2-specific functionality | ZTE, Sanechips |
| R2-2310012 | Discussion on UE-to-UE Relay | Spreadtrum Communications |
| R2-2310093 | Discussion on remaining issue of U2U relay | NEC |
| R2-2310139 | Open issues on QoS for U2U | Nokia, Nokia Shanghai Bell |
| R2-2310167 | Open Issues on Discovery, Relay Selection, and SRAP for UE to UE Relays | InterDigital |
| R2-2310168 | QoS and Configuration for L2 UE-to-UE Relays | InterDigital |
| R2-2310226 | Discussion on the remaining issues on L2 U2U relay | China Telecom |
| R2-2310256 | Discussion on U2U SL relay | CMCC |
| R2-2310348 | Discussion on remaining issues on UE-to-UE Relay | Apple |
| R2-2310405 | Remaining issues for U2U relay operation | LG Electronics Inc. |
| R2-2310406 | Control plane procedure for U2U relay operation | LG Electronics Inc. |
| R2-2310486 | Discussion on UE-to-UE relay | Huawei, HiSilicon |
| R2-2310597 | Discussion on Open Issues for U2U relay RRC | Beijing Xiaomi Mobile Software |
| R2-2310613 | Open issues on U2U | Nokia, Nokia Shanghai Bell |
| R2-2310770 | UE-to-UE relay (re)selection | Sony |
| R2-2310779 | Open issues for Discovery and Relay (re)selection | Qualcomm Incorporated |
| R2-2310780 | Layer-2 specific part on U2U Relay | Qualcomm Incorporated |
| R2-2310925 | Discussion on Relay (re)selection and Discovery | Ericsson España S.A. |
| R2-2310926 | Control Plane Procedures for Layer 2 UE-to-UE Relays | Ericsson España S.A. |
| R2-2311017 | Discussion on remaining issues on U2U Relaying | Fraunhofer IIS, Fraunhofer HHI |
| R2-2311038 | Considerations for U2U L2 relay operations | Kyocera |
| R2-2311114 | Discussion on U2U relay | Kyoto University, SHARP |
| R2-2311174 | SRAP design for U2U Sidelink Relay: remaining issues | Samsung R&D Institute UK |
| R2-2311175 | remaining issues for U2U relay | Sharp |
| R2-2311384 | [Draft] LS on L2ID and User Info for L2 based U2U | LG Electronics Inc. |
| R2-2311385 | Summary of [AT123bis][421][Relay] U2U discovery and (re)selection (ZTE) | ZTE (Rapporteur) |
| R2-2311531 | Summary report of [AT123bis] [421] [Relay] U2U discovery and (re)selection | ZTE |
| R2-2311566 | LS on L2ID and User Info for L2 based U2U | RAN2 |
| 7.9.3 | Service continuity enhancements for L2 UE-to-network relay | |
| R2-2309614 | Further Consideration on Service Continuity Enhancements | CATT |
| R2-2309823 | Remaining issues on service continuity enhancement for L2 U2N relay | vivo |
| R2-2309971 | Discussion on L2 U2N Relay service continuity | Samsung |
| R2-2309977 | Further discussion on service continuity for SL relay | ZTE, Sanechips |
| R2-2310227 | Additional text proposal for the introduction of R18 SL relay service continuity in TS 38.331 | China Telecom |
| R2-2310257 | Remaining issues on service continuity | CMCC |
| R2-2310286 | Discussion on Remaining Issues of Service Continuity | NEC Corporation |
| R2-2310349 | Discussion on path switching to IDLE/INACTIVE relay | Apple |
| R2-2310702 | SL Relay service continuity considerations | Nokia, Nokia Shanghai Bell |
| R2-2310771 | Service continuity enhancements for UE sidelink relay | Sony |
| R2-2310927 | Discussion on Inter-gNB Service Continuity | Ericsson España S.A. |
| R2-2311008 | Discussion on Service Continuity | Huawei, HiSilicon |
| R2-2311176 | Remaining issues for i2i path switching | Sharp |
| 7.9.4 | Multi-path relaying | |
| R2-2309588 | Discussion on Path addition and change for multipath Scenario-1 | NEC |
| R2-2309615 | Remaining issues on Multi-path | CATT |
| R2-2309681 | Discussion on control plane procedure of multi-path relay | OPPO |
| R2-2309682 | Discussion on user plane procedure of multi-path relay | OPPO |
| R2-2309756 | Discussion on remaining issues for multi-path relaying | LG Electronics France |
| R2-2309804 | Discussion on multi-path scenario 1 | Xiaomi |
| R2-2309805 | Discussion on multi-path scenario 2 | Xiaomi |
| R2-2309824 | Remaining Issues for Multi-path | vivo |
| R2-2309825 | Authorization for Multi-path Scenario 2 | vivo, Qualcomm incorporated |
| R2-2309888 | Remaining issue on BSR reporting for Multi-path Scenario 2 | ASUSTeK |
| R2-2309928 | Failure handling in indirect path addition and change | Lenovo |
| R2-2309929 | Discussion on direct path addition | Lenovo |
| R2-2309978 | Further discussion on the support of multi-path relaying | ZTE, Sanechips |
| R2-2309980 | Discussion on remaining issues on multiple path for sidelink relay | Samsung |
| R2-2310013 | Discussion on multi-path relaying | Spreadtrum Communications |
| R2-2310160 | Discussion on Multi-path relaying | Lenovo |
| R2-2310169 | Remaining User Plane Aspects for Multipath | InterDigital |
| R2-2310170 | Remaining Control Plane Aspects for Multipath | InterDigital |
| R2-2310258 | Discussion on indrect path change in scenario 2 | CMCC, Huawei, HiSilicon, Qualcomm, ZTE, NEC, Samsung, Lenovo |
| R2-2310259 | Remaining issues on multi-path | CMCC |
| R2-2310287 | Discussion on UP Issues of Multi-path Relaying | NEC Corporation |
| R2-2310350 | Summary of [Post123][407][Relay] Path addition/change in multi-path for Scenario 1 | Apple |
| R2-2310351 | Discussion on Case G Support in Multi-path Scenario 2 | Apple, Ericsson, Nokia, Nokia Shanghai Bell, Kyocera, LG Electronics |
| R2-2310352 | Discussion on remaining issues for Multi-path Relay | Apple |
| R2-2310468 | Discussion on multi-path scenario 1 | III |
| R2-2310487 | CP remaining issues on multi-path operation | Huawei, HiSilicon |
| R2-2310488 | UP remaining issues on multi-path operation | Huawei, HiSilicon |
| R2-2310772 | Multi-path relaying discussion | Sony |
| R2-2310781 | Open issues on multi-path relay for scenario 1 and scenario 2 | Qualcomm Incorporated |
| R2-2310815 | Discussion on control plane open issues of multi-path relaying | China Telecom |
| R2-2310876 | Discussion on Multi-path | Nokia, Nokia Shanghai Bell |
| R2-2310928 | Discussion on Multipath Relays | Ericsson España S.A. |
| R2-2311039 | Considerations for multipath relay operations for Scenario 1 | Kyocera |
| R2-2311109 | Discussion on user plane open issues of multi-path relaying | China Telecom |
| R2-2311177 | remaining issues for multi-path relay | Sharp |
| R2-2311178 | scenario 2 specific issues for multi-path relay | Sharp |
| R2-2311392 | Offline-429 Summary | Apple |
| 7.10 | IDC enhancements for NR and MR-DC | |
| R2-2310426 | Correction to 38.300 running CR on IDC | vivo,xiaomi |
| R2-2310585 | Introduction of In-Device Co-existence (IDC) enhancements for NR | Xiaomi |
| R2-2311007 | Corrections for 38.331 Running CR for IDC Enhancements | Huawei, HiSilicon |
| R2-2311046 | Correction on the IDC Reporting | ZTE Corporation, Sanechips |
| R2-2311410 | Summary of [AT123bis][701][IDC] Corrections on TS 38.331 and TS 38.300 Agreed in principle CR (Xiaomi) | Xiaomi |
| R2-2311411 | Introduction of In-Device Co-existence (IDC) enhancements for NR | Xiaomi |
| R2-2311412 | Introduction of In-Device Co-existence (IDC) enhancements for NR | Huawei, HiSilicon |
| 7.11.1 | Organizational | |
| R2-2309425 | Reply LS on multicast reception in RRC_INACTIVE (R1-2308612; contact: Apple) | RAN1 |
| R2-2309555 | Open issue list for NR MBS enhancements | CATT, Huawei, HiSilicon, Apple, vivo, Xiaomi, CMCC |
| R2-2309561 | Introduction of eMBS UE Capabilities into TS 38.306 | vivo |
| R2-2309562 | Introduction of eMBS UE Capabilities into TS 38.331 | vivo |
| R2-2309567 | Further Consideration on UE Capability of eMBS | vivo |
| R2-2310310 | MAC Running CR for eMBS | Apple |
| R2-2310711 | RRC running CR for eMBS | Huawei, HiSilicon |
| R2-2311402 | [Draft]LS on UE Capability of FDMed between Multicast MCCH and PBCH | vivo |
| R2-2311542 | LS on UE Capability of Multicast Reception in RRC_INACTIVE | RAN2 |
| 7.11.2.1 | Control plane | |
| R2-2309538 | Leftover CP issues on Multicast reception in RRC_INACTIVE | ZTE, Sanechips |
| R2-2309556 | Report of [Post123][606][eMBS] Session activation deactivation and state transitions | CATT |
| R2-2309557 | Remaining CP Issues for Multicast reception in RRC_INACTIVE | CATT, CBN |
| R2-2309564 | Discussion on Remaining Issues for eMBS CP | vivo |
| R2-2309801 | Remaining control plane issues for multicast reception in RRC INACTIVE | MediaTek inc. |
| R2-2309837 | Further discussion on control plane for multicast reception in RRC_INACTIVE state | TD Tech, Chengdu TD Tech |
| R2-2309846 | MCCH change notification for multicast sessions in RRC_INACTIVE state | TD Tech, Chengdu TD Tech |
| R2-2309859 | Remaining issues on PTM configuration and notification | LG Electronics Inc. |
| R2-2309860 | Remaining issues on multicast servic continuity | LG Electronics Inc. |
| R2-2309946 | Control plane aspects of multicast reception in RRC_INAVTICE | Lenovo |
| R2-2310015 | Discussion on Service Continuity and RRC state transitions | Spreadtrum Communications |
| R2-2310048 | Consideration on the control plane issue for multicast reception in RRC_INACTIVE | Xiaomi |
| R2-2310059 | Discussion on control plane for multicast reception in RRC_INACTIVE | NEC Corporation. |
| R2-2310087 | CP aspects for Multicast reception in RRC_INACTIVE | Samsung R&D Institute India |
| R2-2310265 | Discussion on CP open issues | CMCC |
| R2-2310311 | CP issues for multicast reception in RRC INACTIVE | Apple |
| R2-2310549 | Coexistence of SDT and Multicast reception in RRC_INACTIVE | Sharp |
| R2-2310550 | RRC Resume Due to Bad Reception Quality of Multicast | Sharp |
| R2-2310574 | Discussion on co-existence between multicast reception in INACTIVE and SDT | ITRI |
| R2-2310712 | CP issues for multicast reception for RRC INACTIVE UE | Huawei, HiSilicon |
| R2-2310797 | Control plane details for multicast reception in RRC_INACTIVE state | Nokia, Nokia Shanghai Bell |
| R2-2311034 | Remaining aspects of RRC state transition and notifications not concluded by [Post123][606] | Qualcomm Incorporated |
| R2-2311065 | Consideration of RRC Resume due to bad quality and resume cause | Kyocera |
| R2-2311066 | Other CP open issues for multicast reception in INACTIVE | Kyocera |
| R2-2311092 | Discussion on PTM configuration for eMBS | Shanghai Jiao Tong University |
| R2-2311236 | Multicast reception in RRC_INACTIVE | Ericsson |
| R2-2311237 | MBS multicast and UE power saving | Ericsson |
| R2-2311257 | Report of [Post123][606][eMBS] Session activation deactivation and state transitions | CATT |
| R2-2311403 | Report of [AT123bis][605][eMBS] Session activation/deactivation and state transitions (CATT) | CATT |
| R2-2311404 | Report of [AT123bis][606][eMBS] MRBs handling (Huawei) | Huawei, HiSilicon |
| 7.11.2.2 | User plane | |
| R2-2309539 | Leftover UP issues on Multicast reception in RRC_INACTIVE | ZTE, Sanechips |
| R2-2309540 | CFR design for Multicast reception in RRC_INACTIVE | ZTE, Sanechips |
| R2-2309558 | Remaining UP Issues for Multicast reception in RRC_INACTIVE | CATT, CBN |
| R2-2309565 | Discussion on Remaining Issues for eMBS UP | vivo |
| R2-2309587 | Remaining UP issues for multicast in RRC Inactive | NEC |
| R2-2309802 | Remaining User plane issues for multicast reception in RRC INACTIVE | MediaTek inc. |
| R2-2309845 | Further discussion on user plane for multicast reception in RRC_INACTIVE state | TD Tech, Chengdu TD Tech |
| R2-2309947 | User plane aspects of multicast reception in RRC_INAVTICE | Lenovo |
| R2-2310016 | Discussion on UP remaining issues for Multicast | Spreadtrum Communications |
| R2-2310058 | Discussion on the data loss during the PDCP count synchronization | Xiaomi |
| R2-2310266 | Discussion on UP open issues | CMCC |
| R2-2310312 | UP issues for multicast reception in RRC INACTIVE | Apple |
| R2-2310476 | Views on the FFS on the multicast CFR configuration aspects | Qualcomm Incorporated |
| R2-2310478 | UP Aspects for Multicast Reception | Samsung |
| R2-2310551 | MRB Handling During the RRC State Transition | Sharp |
| R2-2310700 | Discussion on user plane open issues for eMBS | LG Electronics Inc. |
| R2-2310713 | UP issues for multicast reception for RRC INACTIVE UE | Huawei, HiSilicon |
| R2-2310930 | Remaining UP issues for MBS | Ericsson |
| R2-2310991 | User plane aspects of multicast reception in RRC_INACTIVE state | Nokia, Nokia Shanghai Bell |
| R2-2311405 | Report on [AT123bis][607][eMBS] PDCP COUNT synchronization details (ZTE) | ZTE, Sanechips |
| 7.11.3 | Shared processing for MBS broadcast and Unicast reception | |
| R2-2309559 | Remaining Issues on Shared Processing | CATT, CBN |
| R2-2309566 | Bandwidth Location Issue for Shared Processing Report | vivo |
| R2-2310060 | Discussion on shared process between broadcast and unicast | NEC Corporation. |
| R2-2310088 | Shared processing for broadcast and unicast reception | Samsung R&D Institute India |
| R2-2310267 | Discussion on shared processing | CMCC |
| R2-2310586 | Discussion on the CFR location for shared MBS capability | Xiaomi |
| R2-2310714 | Discussion on shared processing for MBS broadcast and unicast reception | Huawei, HiSilicon |
| R2-2311006 | Additional scenarios for shared processing | Nokia, Nokia Shanghai Bell |
| R2-2311049 | Remaining aspects of shared processing for MBS broadcast and unicast reception | Qualcomm Incorporated |
| R2-2311259 | [Pre123bis][601][eMBS] Summary of 7.11.3 Shared processing | Qualcomm Incorporated (Rapporteur) |
| R2-2311406 | Report of [AT123bis][608][eMBS] Shared processing (Qualcomm) | Qualcomm Incorporated |
| 7.12.1 | Organizational | |
| R2-2309475 | Reply LS CAG solution for mobile IAB (S2-2309998; contact: Ericsson) | SA2 |
| R2-2309826 | Running CR for introduction of mobile IAB in TS 38.340 (including open issue list) | Huawei, HiSilicon |
| R2-2310082 | On impacts to BAP spec | CATT, Apple |
| R2-2310120 | 38.306 running CR for mobile IAB capabilities | Nokia, Nokia Shanghai Bell |
| R2-2310121 | 38.331 running CR for mobile IAB capabilities | Nokia, Nokia Shanghai Bell |
| R2-2310188 | Updated workplan for Rel-18 mobile IAB | Qualcomm Inc. (Rapporteur) |
| R2-2310893 | RRC running CR for mobile IAB | Ericsson |
| R2-2310894 | RRC open issues list for mobile IAB | Ericsson |
| R2-2311181 | Mobile IAB node vs IAB node: how to capture the distinction in specifications | Samsung R&D Institute UK |
| R2-2311284 | Running CR for introduction of mobile IAB in TS 38.340 (including open issue list) | Huawei, HiSilicon |
| R2-2311286 | Report from [AT123bis][507][mIAB] Support of RACH-less HO (Samsung) | Samsung |
| R2-2311537 | Summary of [AT123bis][506][mIAB] BAP (HW) | Huawei |
| R2-2311596 | Running CR for introduction of mobile IAB in TS 38.340 (including open issue list) | Huawei, HiSilicon |
| R2-2311608 | 38.304 running CR for R18 mIAB | Intel Corporation |
| R2-2311613 | Running CR to TS 38300 for introduction of mobile IAB | Qualcomm |
| R2-2311617 | Running CR for introduction of mobile IAB in TS 38.340 (including open issue list) | Huawei, HiSilicon |
| 7.12.2.1 | Connected mode | |
| R2-2309798 | Remaining issues of mobility enhancements for mobile IAB | NEC Corporation |
| R2-2310122 | Connected mode issues for mobile IAB | Nokia, Nokia Shanghai Bell |
| R2-2310190 | Enhancements for mobile IAB connected mode mobility | Qualcomm Inc. |
| R2-2310630 | Discussion on mIAB connected mode aspects | Samsung Electronics Polska |
| R2-2311077 | Resolving open issues - CondEventT1 and mIAB indication during connection setup | LG Electronics |
| 7.12.2.1.1 | Reuse of NR NTN RACH-less Handover | |
| R2-2310895 | Rapporteur resolution proposals for mIAB RRC open issues | Ericsson |
| R2-2311179 | IAB MAC rapporteur views on MAC impact of RACH-less HO for mIAB and alignment with NTN | Samsung R&D Institute UK |
| 7.12.2.1.2 | Other | |
| R2-2309827 | Connected mode enhancement for mobile IAB | Huawei, HiSilicon |
| R2-2309939 | Mobility enhancements for mobile IAB-node and its connected UE | Lenovo |
| R2-2309972 | Discussion on mobility enhancement for UE in connected mode | ZTE, Sanechips |
| R2-2310025 | Mobile IAB general aspects and mobility enhancement for connected UEs | Intel Corporation |
| R2-2310302 | Remaining issues on CONNECTED mobility in mobile IAB | Apple |
| R2-2310303 | UE on-board status identification and reporting | Apple, Huawei, HiSilicon, Lenovo, CATT, InterDigital Inc. |
| R2-2311132 | Time-based CHO enhancement for Mobile IAB | AT&T |
| 7.12.2.2 | Idle/Inactive mode | |
| R2-2309828 | Idle/Inactive mode mobility enhancement for mobile IAB | Huawei, HiSilicon |
| R2-2309940 | Mobility enhancement for UE in idle or inactive mode | Lenovo |
| R2-2309973 | Discussion on mobility enhancement for UE in idle or inactive mode | ZTE, Sanechips |
| R2-2310026 | UE cell (re)selection and mIAB CAG | Intel Corporation |
| R2-2310075 | Cell reselection prioritization for mobile IAB cells | Samsung Guangzhou Mobile R&D |
| R2-2310081 | Idle mode mobility for mobile IAB | CATT |
| R2-2310123 | Cell reselection issues for UEs in mobile IAB scenarios | Nokia, Nokia Shanghai Bell |
| R2-2310191 | Enhancements for mobile IAB idle and inactive mode mobility | Qualcomm Inc. |
| R2-2310304 | Remaining issues on IDLE INACTIVE mobility in mobile IAB | Apple |
| R2-2310589 | Discussion on the mIAB access to the network | Xiaomi |
| R2-2310590 | Assistance information for prioritizing mobile IAB cell | Xiaomi |
| R2-2310773 | Mobile IAB cell indication to UE behaviour | Sony |
| R2-2310896 | Indication of DU-migration to UEs in IDLE and INACTIVE | Ericsson |
| R2-2311018 | UE cell reselection prioritization for mobile IAB | SHARP Corporation |
| R2-2311067 | IDLE/INACTIVE mode mobility enhancements for mobile IAB | Kyocera |
| R2-2311075 | Access restriction for mIAB cell | LG Electronics |
| R2-2311076 | Cell reselection and PCI list of IAB cells | LG Electronics |
| R2-2311133 | Inter-frequency cell reselection enhancements for Mobile IAB | AT&T |
| R2-2311573 | [AT123bis][508][mIAB] Cell reselection and PCI list of IAB cells (LGE) | LG Electronics (rapporteur) |
| 7.12.3 | Other | |
| R2-2309829 | Open issues on UE capability and RANU for mobile IAB | Huawei, HiSilicon |
| R2-2309974 | Discussion on remaining issues for mobile IAB | ZTE, Sanechips |
| R2-2310027 | Discussion on mIAB-MT UE capability | Intel Corporation |
| R2-2310083 | On UE capabilities for mIAB | CATT |
| R2-2310124 | Summary of [Post123][051][mIAB] Running CRs UE caps (Nokia) | Nokia, Nokia Shanghai Bell |
| R2-2310189 | Mobile IAB-node connecting to Rel-16/17 IAB cell | Qualcomm Inc. |
| R2-2310591 | Clarification on the mIAB connection to the legacy IAB-donor | Xiaomi |
| R2-2310774 | PCI collision in mobile IAB | Sony |
| R2-2310897 | Conclusions of CAG feature for mobile IAB | Ericsson |
| 7.13.1 | Organizational | |
| R2-2309437 | LS on RACH enhancement (R3-234643; contact: Huawei) | RAN3 |
| R2-2309439 | Reply LS on SHR and SPR (R3-234716; contact: Huawei) | RAN3 |
| R2-2309442 | LS on MDT for NPN (R3-234744; contact: Ericsson) | RAN3 |
| R2-2310446 | Running CR 38306 for UE capability for R18 SONMDT | CATT, Huawei, HiSilicon |
| R2-2310447 | Running CR 38331 for UE capability for R18 SONMDT | CATT, Huawei, HiSilicon |
| R2-2310496 | Running 38.331 CR for logged MDT enhancements and NPN | Huawei, HiSilicon |
| R2-2310497 | Running 36.331 CR for logged MDT enhancements | Huawei, HiSilicon |
| R2-2310498 | Discussion on 38.331 issues for NPN | Huawei, HiSilicon |
| R2-2310508 | Running CR 36306 for UE capability for R18 SONMDT | Huawei, HiSilicon, CATT |
| R2-2310509 | Running CR 36331 for UE capability for R18 SONMDT | Huawei, HiSilicon, CATT |
| R2-2310562 | Running 36331 CR for SN RACH report | ZTE Corporation, Sanechips |
| R2-2310563 | Running 38.331 CR for SON on RACH report | ZTE Corporation, Sanechips |
| R2-2310564 | Reply RAN3 LS on RACH enhancements | ZTE Corporation, Sanechips |
| R2-2310749 | Running CR 36331 for Rel-18 SON MRO | Ericsson |
| R2-2310750 | Running CR 38331 for Rel-18 SON MRO | Ericsson |
| R2-2310751 | List of Open Issues of Rel-18 SONMDT WI | Ericsson |
| R2-2311580 | [] | CMCC |
| R2-2311612 | Reply LS on RACH enhancement | RAN2 |
| 7.13.2 | MRO for inter-system handover for voice fallback | |
| R2-2310744 | Discussion on voice fallback HO failure | Ericsson |
| 7.13.4 | SHR and SPCR | |
| R2-2309672 | Remaining issues on SPR | vivo |
| R2-2309941 | Discussion on inter-RAT SHR from NR to LTE | Lenovo |
| R2-2309942 | SON enhancements for SPR | Lenovo |
| R2-2310365 | Further discussion on inter-RAT SHR and SPR | CATT |
| R2-2310422 | Remain issues on SPR | SHARP Corporation |
| R2-2310501 | Discussion on SHR and SPCR (RAN3 LS R3-234716) | Huawei, HiSilicon |
| R2-2310502 | Discussion on leftover issues for SHR and SPCR | Huawei, HiSilicon |
| R2-2310565 | Consideration on SHR and SPR remaining issues | ZTE Corporation, Sanechips |
| R2-2310595 | SON/MDT enhancements for Inter-RAT SHR and SPR | Samsung |
| R2-2310615 | Clearing SPR configuration | Samsung |
| R2-2310703 | SPR configuration and reporting related issues | Nokia, Nokia Shanghai Bell |
| R2-2310704 | Correlation of inter-RAT SHR with RLF Report | Nokia, Nokia Shanghai Bell |
| R2-2310746 | Discussion on inter-RAT SHR and SPR | Ericsson |
| R2-2311084 | Discussion on successful PSCell change report | Qualcomm Incorporated |
| R2-2311520 | Pre-meeting summary for 7.13.4 (SHR and SPCR) (Nokia) | Nokia (Rapporteur) |
| R2-2311525 | [At123bis][653][R18 SON/MDT] Open issues on SHR and SPCR (Ericsson) | Ericsson (moderator) |
| R2-2311528 | [DRAFT] Reply LS on SHR and SPR | Nokia |
| R2-2311593 | Reply LS on SHR and SPR | RAN2 |
| 7.13.5 | SON for NR-U | |
| R2-2309943 | Discussion on MRO for NR-U | Lenovo |
| R2-2310260 | SONMDT enhancement for NR-U | CMCC |
| R2-2310345 | On lbt-FailureRecoveryConfig in RLF-Report | Apple |
| R2-2310366 | SON Enhancement for NR-U | CATT |
| R2-2310503 | Discussion on leftover issues for SON for NR-U | Huawei, HiSilicon |
| R2-2310612 | SON/MDT enhancements for NR-U | Samsung |
| R2-2311083 | Discussion on RA-Report enhancement for NR-U | Qualcomm Incorporated |
| R2-2311200 | Enhancements of SON reports for NR-U | Ericsson |
| R2-2311204 | [Post123][558][R18 SON/MDT] SON for NR-U (Ericsson) | Ericsson |
| 7.13.6 | RACH enhancement | |
| R2-2310049 | Consideration on the SON enhancements for RACH report | Xiaomi |
| R2-2310272 | Discussion on RACH Enhancement for SONMDT | CMCC |
| R2-2310344 | RACH enhancements remaining issues | Apple |
| R2-2310367 | RACH enhancement for SON | CATT |
| R2-2310423 | Power information in RA report | SHARP Corporation |
| R2-2310428 | RA report enhancement for SDT | SHARP Corporation |
| R2-2310434 | [Draft] Reply LS on RACH enhancement | CMCC |
| R2-2310500 | Discussion on RACH enhancement (RAN3 LS R3-234643) | Huawei, HiSilicon |
| R2-2310504 | Discussion on leftover issues for RACH enhancement | Huawei, HiSilicon |
| R2-2310566 | Consideration on RACH partitioning enhancements | ZTE Corporation, Sanechips |
| R2-2310567 | Consideration on other RACH enhancements | ZTE Corporation, Sanechips |
| R2-2310614 | SON/MDT enhancements for RACH | Samsung |
| R2-2310649 | Discussion on RACH enhancement for SON | NEC |
| R2-2310705 | Discussion on RACH enhancement for SON and reply LS proposal to R2-2309437/R3-234643 | Nokia, Nokia Shanghai Bell |
| R2-2310748 | RA report enhancement | Ericsson |
| R2-2310792 | Discussion on RACH enhancement | China Telecom Corporation Ltd. |
| R2-2311085 | Discussion on RA-Report enhancement for RACH partitioning information | Qualcomm Incorporated |
| R2-2311521 | Summary of the AI 7.13.6 RACH optimization (Ericsson) | Ericsson |
| R2-2311524 | Summary of [At123bis][651][R18 SON/MDT] Views on options in R2-2309437 | CMCC (moderator) |
| 7.13.7 | SON/MDT enhancements for Non-Public Networks | |
| R2-2310050 | Discussion on the SONMDT enhancement for NPN | Xiaomi |
| R2-2310261 | SONMDT enhancement for NPN | CMCC |
| R2-2310343 | Out-of-coverage in NP | Apple |
| R2-2310368 | SON and MDT Enhancement for NPN | CATT |
| R2-2310445 | Summary of [Post123][559][R18 SONMDT] Open issues of SONMDT for NPN (CATT) | CATT |
| R2-2310505 | Discussion on leftover issues for SONMDT enhancements for NPN | Huawei, HiSilicon |
| R2-2310568 | Consideration on SON-MDT support for NPN | ZTE Corporation, Sanechips |
| R2-2310598 | SON/MDT enhancements for NPN | Samsung |
| R2-2310747 | SON Support for NPN | Ericsson |
| R2-2311522 | Pre-meeting summary of 7.13.7 | Huawei (email rapporteur) |
| R2-2311526 | Reply LS on potential override of logged MDT reports upon moving from SNPN to PLMN | RAN2 |
| R2-2311527 | Offline report of [At123bis][654][R18 SON/MDT] RAN2 decision on SONMDT for NPN (Huawei) | Huawei (email rapporteur) |
| R2-2311530 | Pre-meeting summary of 7.13.7 | Huawei (email rapporteur) |
| 7.13.8 | Other | |
| R2-2309673 | Remaining issues on MRO for CPAC | vivo |
| R2-2309944 | SON enhancements for CPAC | Lenovo |
| R2-2309945 | MRO for fast MCG link recovery | Lenovo |
| R2-2310282 | SON MDT enhancement for MR-DC CPAC | CMCC |
| R2-2310283 | MHI Enhancement for SCG Activation/Deactivation | CMCC |
| R2-2310369 | Discussion on Fast MCG recovery MRO Enhancement | CATT |
| R2-2310370 | Discussion on MHI Enhancement for SCG Deactivation/Activation | CATT |
| R2-2310427 | Discussion on fast MCG recovery MRO | SHARP Corporation |
| R2-2310499 | Report of [Post123][567][R18 SONMDT] Cap of SONMDT (Huawei) | Huawei, HiSilicon |
| R2-2310506 | Discussion on leftover issues for fast MCG recovery | Huawei, HiSilicon |
| R2-2310507 | Discussion on leftover issues for CPAC MRO | Huawei, HiSilicon |
| R2-2310569 | Consideration on fast MCG recovery and CPAC MRO | ZTE Corporation, Sanechips |
| R2-2310594 | Fast MCG Link Recovery Optimization | Samsung |
| R2-2310706 | Improvement of handling of timeConnFailure | Nokia, Nokia Shanghai Bell |
| R2-2310707 | MRO for CPAC | Nokia, Nokia Shanghai Bell |
| R2-2310708 | MRO for fast MCG recovery | Nokia, Nokia Shanghai Bell |
| R2-2310745 | Discussion on Fast MCG recovery and SCG failure optimization | Ericsson |
| R2-2310756 | Discussion on CPAC failure report | NTT DOCOMO, INC. |
| R2-2311087 | Discussion on open issues on CPAC MRO and fast MCG recovery failures | Qualcomm Incorporated |
| R2-2311523 | Summary of 7.13.8 Other | ZTE Corporation, Sanechips |
| 7.14.1 | Organizational | |
| R2-2309443 | LS on QMC support in RRC_IDLE and RRC_INACTIVE (R3-224745; contact: Ericsson) | RAN3 |
| R2-2309444 | Reply LS on area scope for QoE measurements (R3-234746; contact: Samsung) | RAN3 |
| R2-2309445 | LS on RAN3 progress on QoE in NR-DC (R3-234750; contact: ZTE) | RAN3 |
| R2-2309478 | Reply LS on area scope for QoE measurements (S4-231490; contact: Huawei) | SA4 |
| R2-2309479 | Reply LS on buffer level threshold-based RVQoE reporting (S4-231582; contact: Apple) | SA4 |
| R2-2309481 | Reply LS on the feasibility of introducing assistance information for handling of QoE reporting during RAN overload (S5-235542; contact: Huawei) | SA5 |
| R2-2309482 | Reply LS on Approval of eQoE CRs for NR (S5-235772; contact: Ericsson) | SA5 |
| R2-2309483 | Reply LS on collecting QoE measurements per MBS service area and MBS session ID (S5-235781; contact: Huawei) | SA5 |
| R2-2309484 | Reply LS on area scope for QoE measurements (S5-235782; contact: Huawei) | SA5 |
| R2-2310201 | Revised Work Plan for Rel-18 NR QoE Enhancement | China Unicom |
| R2-2310204 | [Post123][QoE] Remaining Open Issues (China Unicom) | China Unicom |
| R2-2310653 | 37.340 Running CR to support QoE in NR-DC | Nokia, Nokia Shanghai Bell |
| R2-2310755 | Running CR for QoE enhancements in NR | Ericsson |
| 7.14.2 | QoE measurements in RRC_IDLE INACTIVE | |
| R2-2310203 | Discussion on QoE measurements in RRC_IDLE and INACTIVE states | China Unicom |
| R2-2310240 | Remaining issues on QoE in RRC_IDLE and RRC_INACTIVE | CMCC |
| R2-2310448 | Discussion on remaining issues for QoE measurements in RRC IDLE and INACTIVE state | CATT |
| R2-2310455 | Discussion on QoE measurement in RRC_IDLE and RRC_INACTIVE | Samsung |
| R2-2310514 | Discussion on QoE measurements in RRC_IDLE/INACTIVE | Huawei, HiSilicon |
| R2-2310517 | Discussion on area scope handling for MBS QoE | Huawei, HiSilicon |
| R2-2310570 | Consideration on QoE measurement in IDLE and INACTIVE | ZTE Corporation, Sanechips |
| R2-2310654 | Further discussion on QoE for RRC IDLE and INACTIVE | Nokia, Nokia Shanghai Bell |
| R2-2310752 | QoE measurements in RRC_INACTIVE and RRC_IDLE | Ericsson |
| R2-2310782 | Open issues on QoE collection for IDLE and Inactive state | Qualcomm Incorporated |
| R2-2311400 | Reply LS on area scope for QoE measurements | RAN2 |
| R2-2311401 | [DRAFT] Reply LS on QMC support in RRC_IDLE and RRC_INACTIVE | China Unicom |
| R2-2311409 | Reply LS on QMC support in RRC_IDLE and RRC_INACTIVE | RAN2 |
| 7.14.3 | Rel-17 leftover topics for QoE | |
| R2-2310336 | Views on Way Forward of Buffer Level Threshold Based RVQoE Reporting | Apple |
| 7.14.4 | Support of QoE measurements for NR-DC | |
| R2-2310202 | Discussion on QoE configuration and reporting for NR-DC | China Unicom |
| R2-2310241 | Remaining issues on QoE in NR-DC | CMCC |
| R2-2310449 | Discussion on remaining issues for QoE measurements for NR-DC | CATT |
| R2-2310453 | Discussion on QoE measurements for MR-DC | NEC |
| R2-2310456 | Discussion on QoE measurement for NR-DC | Samsung |
| R2-2310515 | Discussion on QoE measurements in NR-DC | Huawei, HiSilicon |
| R2-2310571 | Consideration on QoE measurement for NR-DC | ZTE Corporation, Sanechips |
| R2-2310655 | Remaining details on QoE support in NR-DC | Nokia, Nokia Shanghai Bell |
| R2-2310753 | QoE measurements in NR-DC | Ericsson |
| R2-2310783 | Open issues to support QoE collection in NR-DC | Qualcomm Incorporated |
| 7.14.5 | UE capabilities and other topics | |
| R2-2310205 | Discussion on Rel-18 NR QoE capabilities | China Unicom |
| R2-2310242 | Discussion on Rel-18 QoE UE Capabilities | CMCC |
| R2-2310243 | 38.306 darft CR for Rel-18 QoE | CMCC |
| R2-2310457 | Discussion on UE capability for MBS QoE buffer | Samsung |
| R2-2310516 | Discussion on UE capabilities for QoE enhancements | Huawei, HiSilicon |
| R2-2310557 | Discussion on remaining issues for UE capability | CATT |
| R2-2310572 | Consideration on Rel-18 other QoE enhancement | ZTE Corporation, Sanechips |
| R2-2310656 | Inter-RAT QoE continuity and UE capabilities | Nokia, Nokia Shanghai Bell |
| R2-2310754 | Measurement status issue in conditional handovers and UE capabilities for QoE | Ericsson |
| R2-2310784 | Discussion on UE QoE capabilities | Qualcomm Incorporated |
| 7.15.1 | Organizational | |
| R2-2309433 | LS on resource selection for MCSt (R1- 2308664; contact: OPPO) | RAN1 |
| R2-2309451 | LS on NR SL unlicensed LBT failures UE behavior (R4-2314351; contact: Ericsson) | RAN4 |
| R2-2309494 | Running PDCP CR for NR Sidelink Evolution | CATT |
| R2-2309495 | PDCP open issue list for Rel-18 NR sidelink evolution | CATT |
| R2-2309504 | Work plan of R18 SL-Evo | OPPO, LG |
| R2-2309505 | Open Issue list for R18 SL-Evo | OPPO, LG |
| R2-2309506 | Running CR of TS 38.331 for SL Evolution | OPPO |
| R2-2309749 | Running CR of TS 38.321 for SL Evolution | LG Electronics Inc. |
| R2-2309750 | Open issue list of stage 3 MAC running CR for R18 SL-Evo | LG Electronics Inc. |
| R2-2310072 | Discussion on UE capability for Rel-18 SL evolution | Huawei, HiSilicon |
| R2-2310073 | Running CR of TS 38.306 for Rel-18 SL evolution | Huawei, HiSilicon |
| R2-2310074 | Running CR of TS 38.331 on UE capability for Rel-18 SL evolution | Huawei, HiSilicon |
| R2-2310128 | Draft LS reply to LS R4-2314351 | Ericsson |
| R2-2310129 | discussion on RAN4 LS R4-2314351 | Ericsson |
| R2-2311495 | Running CR of TS 38.331 for SL Evolution | OPPO (Rapporteur) |
| R2-2311496 | Running CR of TS 38.321 for SL Evolution | LG (Rapporteur) |
| R2-2311497 | Summary of [AT123bis][106][V2XSL] MAC detailed open issues (LG) | LG |
| R2-2311498 | Running PDCP CR for NR Sidelink Evolution | CATT |
| R2-2311499 | Summary on [AT123bis][108][V2X/SL] 38.306 running CR (Huawei) | Huawei, HiSilicon |
| R2-2311500 | Running CR of TS 38.306 for Rel-18 SL evolution | Huawei, HiSilicon |
| R2-2311501 | Running CR of TS 38.331 on UE capability for Rel-18 SL evolution | Huawei, HiSilicon |
| R2-2311504 | Stage 2 Running CR of TS 38.300 for SL Evolution | InterDigital |
| R2-2311583 | LS on a capability of UE power class and IE on PEMAX,CA for SL CA (R4-2317751; contact: LGE & OPPO) | RAN4 |
| 7.15.2 | SL-U | |
| R2-2309496 | Discussion on resource allocation for MCSt and LCP enhancement for COT sharing | CATT, CICTI |
| R2-2309497 | Remaining issues on SL C-LBT failure handling | CATT |
| R2-2309507 | Discussion on C-LBT-F report to peer UE | OPPO, MediaTek Inc., Xiaomi, vivo, NEC, Qualcomm, Samsung, CATT, TCL |
| R2-2309508 | Left issues on SL-U | OPPO |
| R2-2309511 | Summary of [POST123][511] Additional conditions to trigger resource (re)selection (OPPO) | OPPO |
| R2-2309638 | Discussion on SL C-LBT failure and LCP enhancement | Huawei, HiSilicon |
| R2-2309639 | Impact on leftover issues for SL-U | Huawei, HiSilicon |
| R2-2309718 | Discussion on remaining issues of SL-U | LG Electronics Inc. |
| R2-2309744 | Remaining issues on SL LBT failure | vivo |
| R2-2309745 | Remaining issues on resource (re)selection and others for SLU | vivo |
| R2-2309811 | Discussion on LS on NR SL unlicensed LBT failures UE behavior | LG Electronics Inc. |
| R2-2309814 | Discussion on remaining issues on SL-U | Xiaomi |
| R2-2309815 | Discussion on resource allocation and enhanced LCP for SL-U | Xiaomi |
| R2-2309867 | Remaining issues on SL-U | SHARP Corporation |
| R2-2309889 | Discussion on resource (re)selection for MCSt regarding LBT failure | ASUSTeK |
| R2-2309933 | Discussion on resource (re)selection and other remaining issues for NR SL-U | Lenovo |
| R2-2310005 | Discussion on remaining issues of SL-U | Spreadtrum Communications |
| R2-2310051 | Discussion on remaining issues for SL-U | ZTE Corporation, Sanechips |
| R2-2310052 | Discussion on reporting C-LBT failure indication to the peer UE | ZTE Corporation, Sanechips,InterDigital, Lenovo, Nokia |
| R2-2310091 | Discussion on remaining issues of SL-U | NEC |
| R2-2310131 | Remaining aspects on SL-U | Ericsson |
| R2-2310138 | On HARQ DTX and multiple PSFCH occasions | Nokia, Nokia Shanghai Bell |
| R2-2310143 | Remaining details of SL LCP and SL consistent LBT procedure | Lenovo |
| R2-2310159 | Open issues on SL-U | Nokia, Nokia Shanghai Bell |
| R2-2310162 | Reporting Consistent LBT Failure to the Peer UE | InterDigital |
| R2-2310163 | Handling SL RLF due to LBT Failure | InterDigital |
| R2-2310164 | Mode 2 Resource Selection Considering LBT Impacts | InterDigital |
| R2-2310236 | Remaining issue on SL Consistent LBT failure | TCL |
| R2-2310298 | Remaining issues on SL-U | Apple |
| R2-2310431 | Remaining issue on SL DRX in SL-U | ITL |
| R2-2310902 | Discussion on remaining issues of SL-U | Qualcomm India Pvt Ltd |
| R2-2310969 | MAC Issues for SL-U | Samsung Electronics Co., Ltd |
| R2-2310970 | Remaining issues for SL-U | Samsung Electronics Co., Ltd |
| R2-2310971 | Additional ID in COT sharing | Samsung Electronics Co., Ltd |
| R2-2311222 | Left issues on SL-U | OPPO |
| R2-2311253 | Discussion on resource allocation for MCSt and LCP enhancement for COT sharing | CATT, CICTCI |
| R2-2311505 | LS reply to RAN4 LS R4-2314351 | RAN2 |
| 7.15.3 | SL-FR2 | |
| R2-2309498 | Discussion on Sidelink Operation on FR2 | CATT |
| R2-2309509 | Discussion on SL-FR2 impact | OPPO |
| R2-2309716 | Discussion on RAN2 aspects of SL-FR2 | LG Electronics Inc. |
| R2-2309746 | Discussion on RAN2 aspects for FR2 procedure | vivo |
| R2-2309767 | Discussion on SL-FR2 | Huawei, HiSilicon |
| R2-2309806 | Discussion on SL-FR2 impact to RAN2 | Xiaomi |
| R2-2309934 | Discussion on FR2 operation for NR SL | Lenovo |
| R2-2310053 | Discussion on sidelink FR2 | ZTE Corporation,CAICT, Sanechips |
| R2-2310130 | SL in FR2 | Ericsson |
| R2-2310299 | Discussion on RAN2 aspects of SL FR2 | Apple |
| R2-2310463 | Discussion on SL-FR2 aspects in RAN2 | Nokia Netherlands |
| R2-2310903 | Discussion on SL FR2 | Qualcomm India Pvt Ltd |
| 7.15.4 | SL-CA | |
| R2-2309499 | Discussion on NR Sidelink CA | CATT |
| R2-2309510 | Left issues on SL Carrier Aggregation | OPPO |
| R2-2309717 | Discussion on remaining issues of SL-CA enhancements | LG Electronics Inc. |
| R2-2309747 | Discussion on remaining issues on NR Sidelink CA | vivo |
| R2-2309768 | Discussion on SL CA enhancements | Huawei, HiSilicon |
| R2-2309816 | Discussion on carrier aggregation for NR sidelink | Xiaomi |
| R2-2309902 | SL RLF in SL CA | Fujitsu |
| R2-2309935 | Discussion on multi-carrier operation for NR SL | Lenovo |
| R2-2310054 | Discussion on sidelink CA | ZTE Corporation, Sanechips |
| R2-2310092 | Discussion on remaining issues of SL CA | NEC |
| R2-2310094 | Discussion on carrier selection procedure of running CR | NEC |
| R2-2310132 | Aspects of SL CA | Ericsson |
| R2-2310165 | Carrier Aggregation in NR SL for Unicast | InterDigital |
| R2-2310300 | Remaining issues on SL carrier mapping | Apple, ZTE Corporation, Sanechips, Ericsson, InterDigital Inc |
| R2-2310301 | Remaining issues on SL CA | Apple, Ericsson |
| R2-2310878 | Remaining issues in support of sidelink CA | Nokia, Nokia Shanghai Bell |
| R2-2310904 | Discussion on Tx Profile for SL CA | Qualcomm India Pvt Ltd |
| R2-2310905 | Discussion on remaining issues of SL CA | Qualcomm India Pvt Ltd |
| R2-2310972 | Remaining issues for SL-CA | Samsung Electronics Co., Ltd |
| R2-2311056 | Discussion on Tx Profile for SL CA | Qualcomm, Apple |
| R2-2311115 | Left issues on SL Carrier Aggregation | OPPO |
| R2-2311502 | [AT123bis][109][V2X/SL] RRC related open issues for CA/Duplication (OPPO) | OPPO |
| 7.16.1 | Organizational | |
| R2-2309435 | Reply LS on Data Collection Requirements and Assumptions (R1- 2308730; contact: Qualcomm) | RAN1 |
| R2-2311021 | R2 input to TR 38.843 | Ericsson |
| R2-2311022 | Open Issues / Rapporteur Insights | Ericsson |
| 7.16.2.1 | Architecture and General | |
| R2-2309549 | General Aspects for AIML | OPPO |
| R2-2309583 | General aspects of AIML | NEC |
| R2-2309661 | Further discussions on architecture general aspects of AIML for NR air-interface | CATT, Turkcell |
| R2-2309662 | Capability and applicability conditions reporting of AIML for NR air-interface | CATT, Turkcell |
| R2-2309674 | Discussion on Architecture General | vivo |
| R2-2309807 | Discussion on architecture aspects | Xiaomi |
| R2-2309949 | General aspects related to AI based positioning | Lenovo |
| R2-2310009 | Discussion on general architecture | Spreadtrum Communications |
| R2-2310097 | On General Aspect of AI Funtionality based LCM | ZTE Corporation, Sanechips |
| R2-2310098 | On general Aspect of AI Model based LCM | ZTE Corporation, Sanechips |
| R2-2310206 | Discussion on the AI Functional Framework | China Unicom |
| R2-2310207 | Functionality mapping and AI/ML algorithm locality | Intel Corporation |
| R2-2310273 | Discussion on general aspects of AIML framework | CMCC |
| R2-2310294 | Discussion on UE capability, applicability condition reporting and LCM | Apple |
| R2-2310295 | Remaining issues on model ID and AI/ML architecture | Apple |
| R2-2310394 | AI/ML Dependency on Configuration/Condition and Applicability of AI/ML | MediaTek Inc. |
| R2-2310469 | Discussion on AIML Model Applicability | Rakuten Mobile, Inc |
| R2-2310510 | Discussion on applicability conditions | Huawei, HiSilicon |
| R2-2310511 | Discussion on mapping of functionality | Huawei, HiSilicon |
| R2-2310679 | Discussion on AIML applicability condition | NTT DOCOMO, INC. |
| R2-2310692 | Discussion on AI/ML applicability conditions, capability and UE’s internal conditions | SHARP Corporation |
| R2-2310695 | Discussion on AIML UE capability | NTT DOCOMO, INC. |
| R2-2310836 | AIML architecture | Nokia, Nokia Shanghai Bell |
| R2-2310881 | Indication of supported AI/ML functionalities and models | Samsung Electronics Iberia SA |
| R2-2310940 | AI/ML capability reporting | InterDigital |
| R2-2311023 | UE capability/applicability reporting | Ericsson |
| R2-2311100 | AIML method_Architecture General | LG Electronics |
| R2-2311116 | Architecture and general aspects of AI/ML for NR air interface | AT&T |
| R2-2311119 | Open issues in functionality to physical entities mapping | Qualcomm Incorporated |
| R2-2311120 | Towards one LCM | Qualcomm Incorporated |
| R2-2311202 | Function-to-entity mapping | Ericsson |
| 7.16.2.2 | Data Collection | |
| R2-2309550 | Data Collection for UE Side Model | OPPO |
| R2-2309584 | AIML Model Identification and Management | NEC |
| R2-2309585 | AIML Data Collection for Model Training | NEC |
| R2-2309663 | Considerations on data collection of AIML for NR air-interface | CATT, Turkcell |
| R2-2309675 | Remaining issues of data collection | vivo |
| R2-2309808 | Discussion on data collection | Xiaomi |
| R2-2309903 | Discussions on AIML data collection | Fujitsu |
| R2-2309950 | Discussion on data collection aspects | Lenovo |
| R2-2310010 | Discussion on data collection | Spreadtrum Communications |
| R2-2310208 | discussion on data collection enhancement | Intel Corporation |
| R2-2310296 | Further discussion on data collection for AI/ML | Apple |
| R2-2310396 | Data Collection for Model Training at UE Side | MediaTek Inc. |
| R2-2310512 | Discussion on data collection | Huawei, HiSilicon |
| R2-2310775 | Summary of impacts due to data collection | Sony |
| R2-2310837 | Use case specific data collection aspects | Nokia, Nokia Shanghai Bell |
| R2-2310879 | Enhancements for RRM/MDT for AI/ML data collection | Samsung Electronics Iberia SA |
| R2-2311020 | Data collection for AIML | Interdigital Inc. |
| R2-2311057 | MDT Enhancements for offline training in AI/ML Data Collection | Nokia, Nokia Shanghai Bell, MediaTek Inc. |
| R2-2311088 | On Purpose Driven Data Collection | ZTE Corporation, Sanechips |
| R2-2311101 | AIML method_Data Collection | LG Electronics |
| R2-2311117 | Data collection aspects of AI/ML for NR air interface | AT&T |
| R2-2311121 | UE friendly principles for NW data collection | Qualcomm Incorporated |
| R2-2311201 | Data collection for AI/ML | Ericsson |
| R2-2311203 | [Post123][059][AIML] Data Collection (Ericsson) | Ericsson |
| 7.16.2.3 | Control and LCM other | |
| R2-2309525 | AI/ML model delivery | Xiaomi |
| R2-2309551 | Open Issue Discussion on Model Transfer Delivery | OPPO |
| R2-2309552 | Discussion on Model Monitoring | OPPO |
| R2-2309586 | AIML Model transfer | NEC |
| R2-2309664 | Considerations on other model control procedures | CATT, Turkcell |
| R2-2309676 | Discussion on model transfer | vivo |
| R2-2309677 | Discussion on model management | vivo |
| R2-2309866 | Discussion on model model-based management | LG Electronics France |
| R2-2309904 | Discussion on model functionality_control and monitoring | Fujitsu |
| R2-2309951 | Discussion on functionality and model identification | Lenovo |
| R2-2310011 | Discussion on Control and LCM other | Spreadtrum Communications |
| R2-2310209 | Architecture impact on model transfer method | Intel Corporation |
| R2-2310210 | model control procedure: RAN2 impact | Intel Corporation |
| R2-2310274 | Discussion on model control and other LCM procedures | CMCC |
| R2-2310297 | Further discussion on model transfer | Apple |
| R2-2310401 | Discussion on AI/ML Model Transfer/Delivery | MediaTek Inc. |
| R2-2310402 | Model Control and Model Monitoring | MediaTek Inc. |
| R2-2310421 | Discussion on the AI based positioning | Xiaomi |
| R2-2310513 | Discussion on control and LCM other | Huawei, HiSilicon |
| R2-2310539 | AI ML model management across RRC state transitions and mobility among non-interoperable networks | Rakuten Symphony |
| R2-2310776 | Some considerations about CSI compression | Sony |
| R2-2310839 | AIML control and other topics | Nokia, Nokia Shanghai Bell |
| R2-2310880 | AI/ML model transfer/delivery solutions | Samsung Electronics Iberia SA |
| R2-2310882 | AI/ML functionality-based and model-ID based LCM | Samsung Electronics Iberia SA |
| R2-2310941 | AI/ML control and LCM | InterDigital |
| R2-2311024 | Model transfer (Way Forward) | Ericsson |
| R2-2311089 | Further Discussion on Model TransferDelivery for AIML | ZTE Corporation, Sanechips |
| R2-2311118 | AI/ML model transfer and LCM | AT&T |
| R2-2311122 | Unified Life Cycle Management | Qualcomm Incorporated |
| R2-2311143 | Discussion of AI/ML Life Cycle Management | Futurewei Technologies |
| 7.17.1 | Organizational | |
| R2-2309461 | LS on Dual Tx/Rx Multi-SIM (R4-2314465; contact: MediaTek) | RAN4 |
| R2-2309789 | [Post123][MUSIM] Remaining Open Issues (vivo) | vivo |
| R2-2309790 | Running RRC CR for NR MUSIM enhancements | vivo |
| R2-2309891 | Draft running CR to 38.331 for MUSIM UE Capabilities | Huawei, HiSilicon |
| R2-2309892 | Draft running CR to 38.306 for MUSIM UE Capabilities | Huawei, HiSilicon |
| R2-2310918 | 38.300 Running CR for NR MUSIM enhancements | China Telecommunications |
| R2-2310921 | 38.300 Running CR for NR MUSIM enhancements | China Telecommunications |
| R2-2311040 | 37.340 Running CR for Introduction of MUSIM | ZTE Corporation, Sanechips |
| R2-2311294 | 38.300 Running CR for NR MUSIM enhancements | China Telecom |
| R2-2311295 | 37.340 Running CR for Introduction of MUSIM | ZTE Corporation, Sanechips |
| 7.17.2 | Procedures for MUSIM temporary capability restriction | |
| R2-2309553 | Remaining Issues on Procedures for MUSIM Temporary Capability Restriction | OPPO |
| R2-2309715 | Further discussion on the MUSIM temporary capability restriction | China Telecom Corporation Ltd. |
| R2-2309791 | Report of [Post123][234][MUSIM] UE preferred frequency (vivo) | vivo |
| R2-2309793 | Procedures for MUSIM temporary capability restriction | vivo |
| R2-2309890 | Discussion on procedures for temporary capability restriction | Huawei, HiSilicon |
| R2-2310031 | Early capability restriction indication in ResumeRequest | Intel Corporation |
| R2-2310171 | Control signaling for Dual-Active MUSIM | Qualcomm Incorporated |
| R2-2310318 | Procedures for MUSIM temporary capability restriction | Apple |
| R2-2310583 | Timer control for capability restriction | Xiaomi |
| R2-2310592 | Discussion on temporary capability restriction | Samsung |
| R2-2310648 | Procedures for MUSIM temporary capability restriction | NEC |
| R2-2310966 | Indication of restricted capabilities at RRC Setup and Resume by MUSIM UE | Ericsson |
| R2-2310967 | Discussion on MUSIM timers | Ericsson |
| R2-2311014 | Further analysis on signalling procedure for capability restriction | Nokia, Nokia Shanghai Bell |
| R2-2311041 | Consideration on the Temporary Capability Reporting procedure | ZTE Corporation, Sanechips |
| R2-2311098 | Supporting Proactive cases in other scenarios | LG Electronics Inc. |
| R2-2311099 | Procedures for MUSIM temporary capability restriction | DENSO CORPORATION |
| R2-2311107 | Timer based restriction in MUSIM | LG Electronics France |
| R2-2311108 | Timer based restriction in MUSIM | LG Electronics Deutschland |
| R2-2311238 | Indication of restricted capabilities at RRC Setup and Resume by MUSIM UE | Ericsson |
| 7.17.3 | Allowed MUSIM temporary capability restrictions | |
| R2-2309554 | Allowed MUSIM Temporary Capability Restrictions | OPPO |
| R2-2309792 | Discussion on temporary capability restriction for Rel-18 Multi-SIM | vivo |
| R2-2309843 | Details of allowed MUSIM temporary capability restrictions | Huawei, HiSilicon |
| R2-2310090 | Allowed MUSIM temporary capability restrictions | Samsung R&D Institute India |
| R2-2310319 | Aspects of allowed MUSIM temporary capability restriction | Apple |
| R2-2310582 | Clarification on srs-TxSwitch and MIMO-layer for MUSIM | Xiaomi, vivo |
| R2-2310965 | On some restricted capabilities for Rel-18 MUSIM UE | Ericsson |
| R2-2311015 | On specific capabilities for restriction and feature interworking scenarios | Nokia, Nokia Shanghai Bell |
| R2-2311042 | Consideration on the Temporary Capability Reporting | ZTE Corporation, Sanechips |
| 7.17.4 | Other | |
| R2-2309794 | Discussion on MUSIM gap priorities | vivo |
| R2-2309844 | Discussion on MUSIM gaps and UE capabilities | Huawei, HiSilicon |
| R2-2310032 | Feature interaction between R17 and R18 MUSIM | Intel Corporation |
| R2-2310038 | Further discussion on MUSIM gap priorities | Samsung Electronics Czech |
| R2-2310584 | Remaining issues of MUSIM gap | Xiaomi |
| R2-2310917 | MUSIM gap priority handlling | China Telecommunications |
| R2-2311016 | MUSIM Gap collision handling | Nokia, Nokia Shanghai Bell |
| R2-2311043 | Consideration on the MN-SN Coordination for the MUSIM | ZTE Corporation, Sanechips |
| R2-2311135 | Discussion on MUSIM gap priority | MediaTek Inc. |
| 7.18.1 | Organizational | |
| R2-2310114 | Introduction of MT-SDT | ZTE Corporation (rapporteur) |
| R2-2310154 | Outcome of email discussion [POST123][303][MT-SDT] on UE Capabilities for Rel-18 MT SDT | Intel Corporation |
| R2-2310155 | UE Capabilities for Rel-18 MT SDT WI | Intel Corporation |
| R2-2310156 | UE Capabilities for Rel-18 MT SDT WI | Intel Corporation |
| R2-2311185 | Introduction of MT-SDT in Stage-2 | Nokia, Nokia Shanghai Bell |
| 7.18.2 | Control plane aspects | |
| R2-2309569 | Remaining Issues for MT-SDT in CP | vivo |
| R2-2309589 | MT-SDT Control Plane | Ericsson |
| R2-2310106 | MT-SDT UE capability related issues | ZTE Corporation, Sanechips |
| R2-2310144 | remaining CP details for MT-SDT | Lenovo |
| R2-2310727 | Discussion on UE capabilities for MT-SDT | Huawei, HiSilicon |
| R2-2310810 | Discussion on NCD-SSB for MT-SDT | Qualcomm Incorporated |
| 7.18.3 | User plane aspects | |
| R2-2309590 | MT-SDT User Plane | Ericsson |
| R2-2309689 | Remaining UP issues on MT-SDT | LG Electronics Inc. |
| R2-2309771 | Handling SSB failure during SDT Procedure | Samsung Electronics Co., Ltd |
| R2-2310145 | remaining UP details for MT-SDT | Lenovo |
| R2-2310309 | Beam failure detection during RA-SDT | Apple |
| R2-2310450 | Discussion the remaining issues on the UE capability on MT-SDT | CATT |
| R2-2310777 | Remaining issues for MT-SDT | Sony |
| R2-2310811 | Discussion on SSB failure handling in an ongoing RA-SDT | Qualcomm Incorporated |
| R2-2310872 | Beam failure recovery for Rel-18 SDT | Sony, Nokia, Nokia Shanghai Bell, Samsung, Huawei |
| R2-2311186 | Selection between CG-SDT and RACH based SDT | Nokia, Nokia Shanghai Bell |
| 7.19.1 | Organizational | |
| R2-2309408 | Reply LS on INACTIVE eDRX above 10.24sec and SDT (C4-233691; contact: Ericsson) | CT4 |
| R2-2309424 | LS on reduced peak data rate for Rel-18 eRedCap UEs (R1-2308610; contact: Ericsson) | RAN1 |
| R2-2309440 | Reply LS on Rel-18 RedCap enhancements to address remaining ENs in TS 23.502 (R3-234725; contact: Huawei) | RAN3 |
| R2-2309473 | Reply LS on INACTIVE eDRX above 10.24sec and SDT (S2-2309757; contact: Ericsson) | SA2 |
| R2-2309535 | Running CR for TS 38.300 for Rel-18 eRedCap | OPPO |
| R2-2309731 | Running MAC CR for eRedCap | vivo (Rapporteur) |
| R2-2309840 | Running 38.304 CR for enhanced support of reduced capability NR devices | Huawei, HiSilicon |
| R2-2310211 | Outcome of email discussion [POST123][753][eRedCap] on UE Capabilities for Rel-18 eRedCap | Intel Corporation |
| R2-2310212 | [Temporary CR to TS 38.306] [RAN1 lead features] UE capabilities for Rel-18 eRedCap WI | Intel Corporation |
| R2-2310213 | [Temporary CR to TS 38.331] [RAN1 lead features] UE capabilities for Rel-18 eRedCap WI | Intel Corporation |
| R2-2310214 | [RAN2 lead features] UE capabilities for Rel-18 eRedCap WI | Intel Corporation |
| R2-2310215 | [RAN2 lead features] UE capabilities for Rel-18 eRedCap WI | Intel Corporation |
| R2-2311054 | Running RRC CR for eRedCap | Ericsson |
| R2-2311059 | Remaining open issues in Rel-18 eRedCap WI | Ericsson |
| R2-2311239 | Running RRC CR for eRedCap | Ericsson |
| R2-2311436 | Running CR for TS 38.300 for Rel-18 eRedCap | OPPO |
| R2-2311437 | Running 38.304 CR for enhanced support of reduced capability NR devices | Huawei, HiSilicon |
| R2-2311438 | Running MAC CR for eRedCap | vivo (Rapporteur) |
| R2-2311439 | Introduction of eRedCap | Ericsson |
| R2-2311442 | [Temporary CR] [RAN1 lead features] UE capabilities for Rel-18 eRedCap WI | Intel Corporation |
| R2-2311443 | [Temporary CR] [RAN1 lead features] UE capabilities for Rel-18 eRedCap WI | Intel Corporation |
| R2-2311444 | UE capabilities for Rel-18 eRedCap WI | Intel Corporation |
| R2-2311445 | UE capabilities for Rel-18 eRedCap WI | Intel Corporation |
| 7.19.2 | Enhanced eDRX in RRC_INACTIVE | |
| R2-2309732 | Discussion on remaining issues on enhanced eDRX | vivo, Guangdong Genius |
| R2-2309841 | Discussion on open issues for enhanced eDRX | Huawei, HiSilicon, Ericsson |
| R2-2310458 | Remaining issues in enhanced eDRX in RRC_INACTIVE | Samsung |
| R2-2310830 | Remaining issues of enhanced eDRX in RRC_INACTIVE | ZTE Corporation, Sanechips |
| R2-2311060 | Enhanced eDRX in RRC_INACTIVE | Ericsson |
| 7.19.3 | Further reduced UE complexity in FR1 | |
| R2-2309534 | Identification and access restriction for eRedCap Ues | OPPO |
| R2-2309576 | Discussion on RA procedure for eRedCap UEs | OPPO |
| R2-2309697 | Discussion on LCID selection for feature combination | CATT |
| R2-2309733 | Discussion on access restriction for eRedCap | vivo, Guangdong Genius |
| R2-2309734 | Discussion on 2-step RACH for eRedCap | vivo, Guangdong Genius |
| R2-2309809 | Early identification and access restriction for eRedCap UEs | Huawei, HiSilicon |
| R2-2309810 | Discussion on UE capability of eRedCap UEs | Huawei, HiSilicon |
| R2-2310341 | On simplifying RA resource access for (e)RedCap | Apple |
| R2-2310454 | eRedCap UEs behaviour without eRedCap RA-partition | NEC |
| R2-2310459 | eRedCap UE behaviour without eRedCap RA-partition | Samsung |
| R2-2310460 | Remaining issues in further reduced UE complexity in FR1 | Samsung |
| R2-2310604 | Discussion on Msg1-based early indication for Rel-18 eRedCap UE | LG Electronics Inc. |
| R2-2310627 | Discussion on eRedCap UEs behavior with RA-partition | Xiaomi Communications |
| R2-2310645 | Discussion on remaining issues on early indication for eRedcap | Xiaomi Communications |
| R2-2310723 | Discussion on bit rate and BW reduction for eRedCap | Nokia, Nokia Shanghai Bell, Ericsson, NTT DOCOMO, Intel, Semtech, BT, Deutsche Telekom |
| R2-2310812 | Discussion on further complexity reduction for eRedCap UE | Qualcomm Incorporated |
| R2-2310813 | Discussion on optional UE capability filter for eRedCap UE | Qualcomm Incorporated, Ericsson, Intel, ZTE, Xiaomi |
| R2-2310831 | Remaining issues of Msg1 early indication and access restriction | ZTE Corporation, Sanechips |
| R2-2310832 | Remaining issues of eRedCap UE capabilities | ZTE Corporation, Sanechips |
| R2-2310874 | Resource partition for eRedCap | Nokia, Nokia Shanghai Bell |
| R2-2310875 | Summary of [Post123][756] eRedCap UE behaviour without eRedCap RA partition | Nokia, Nokia Shanghai Bell |
| R2-2311061 | Discussion on capability signaling for eRedCap UEs | Ericsson |
| R2-2311062 | Selection of RA resources for eRedCap UEs | Ericsson |
| R2-2311197 | Msg1 Early Indication for eRedcap | Sequans Communications |
| R2-2311214 | Discussion on eRedCap UEs behavior with RA-partition | Beijing Xiaomi Mobile Software |
| R2-2311219 | Discussion on remaining issues on early indication for eRedcap | Beijing Xiaomi Mobile Software |
| R2-2311428 | WF on selection of RA resource set for eRedCap | Nokia, Nokia Shanghai Bell, Samsung, Xiaomi |
| 7.20.1 | Organizational | |
| R2-2309410 | LS to RAN2 on CBSR for Rel-18 MIMO (R1-2308396; contact: Samsung) | RAN1 |
| R2-2309850 | Running CR for TS 38.321 for MIMO Evolution | Samsung |
| R2-2310611 | Running CR for Introduction of MIMO Evolution | Ericsson |
| R2-2310819 | Report for Post 123 MIMOevo RRC | Ericsson |
| R2-2311127 | Draft 38.300 CR for introduction of 2-TA enhancement | NTT DOCOMO, INC. |
| R2-2311167 | L1 parameter Excel with rapporteur comments MIMOevo | Ericsson |
| R2-2311290 | Report for Post 123 MIMOevo RRC | Ericsson |
| R2-2311291 | [DRAFT] LS on MIMOevo | Ericsson |
| R2-2311292 | Introduction of 2-TA enhancement | NTT DOCOMO, INC. |
| R2-2311609 | LS on MIMOevo | RAN2 |
| 7.20.2 | Two TAs for multi-DCI multi-TRP | |
| R2-2309665 | Discussion on multiple TAG | OPPO |
| R2-2309690 | TAG modeling and TAT expiry in 2TAs mTRP | LG Electronics Inc. |
| R2-2309912 | Consideration on the TAG Indication upon CBRA | CATT |
| R2-2309913 | Discussions on Two TAs for Multi-DCI Multi-TRP | CATT |
| R2-2309953 | Discussion on the impacts of Two TAs for multi-DCI multi-TRP operation | Lenovo |
| R2-2309954 | Discussion on the UE-initiated RACH procedure in multi-TRP operation | Lenovo |
| R2-2309955 | Consideration on RLF in multi-TRP operation | Lenovo |
| R2-2310063 | Open issues on two TAs for multi-DCI multi-TRP | Samsung Research America |
| R2-2310101 | Further Discussion on RACH for mDCI mTRP with 2TA enhancement | ZTE Corporation,Sanechips |
| R2-2310103 | On RRC parameter for mDCI mTRP with 2TA enhancement | ZTE Corporation,Sanechips |
| R2-2310193 | Discussion on two TAs for multiple TRPs | SHARP Corporation |
| R2-2310315 | Support of Two TAs for multi-DCI multi-TRP | Apple |
| R2-2310587 | Remaining issues for 2 TA handling of mTRP | Xiaomi |
| R2-2310809 | Discussion on multi-DCI multi-TRP with two TAs | Qualcomm Incorporated |
| R2-2310847 | UL time alignment in multi-DCI based multi-TRP with two TAs | InterDigital |
| R2-2310932 | MAC issues for multi-DCI multi-TRP with two TAs | Ericsson |
| R2-2311003 | Remaining issues on 2TA for mTRP | Huawei, HiSilicon |
| R2-2311125 | Current status of functional issues on 2TA enhancement | NTT DOCOMO, INC. |
| R2-2311169 | On 2TA operation RRC parts | Ericsson |
| R2-2311187 | RA procedure while SpCell is configured with 2 TAGs | Nokia, Nokia Shanghai Bell |
| R2-2311188 | Handling of two TAGs associated with a Serving Cell | Nokia, Nokia Shanghai Bell |
| R2-2311251 | On 2TA operation | Ericsson |
| R2-2311252 | MAC issues for multi-DCI multi-TRP with two TAs | Ericsson |
| 7.20.3 | Unified TCI extension to mTRP operation | |
| R2-2309666 | Discussion on MAC CE design for mTRP | OPPO |
| R2-2309691 | Discussion on Unified State MAC CE for mDCI | LG Electronics Inc. |
| R2-2309693 | Discussion on Unified State MAC CE for sDCI | LG Electronics Inc. |
| R2-2309743 | Discussion on MAC CE design for MTRP | CEWiT |
| R2-2309849 | Remaining Issues on Single-DCI based unified TCI extension to multi-TRP operation | Samsung |
| R2-2309914 | Discussion on Unified TCI Framework Extension for sDCI and mDCI based Multi-TRP | CATT |
| R2-2310064 | Open issues on MIMO RRC parameters | Samsung Research America |
| R2-2310102 | Further DIscussion on remaining UP issues for MIMO-evo | ZTE Corporation,Sanechips |
| R2-2310906 | Design of MAC CE for Rel-18 MIMO | Nokia. Nokia Shanghai Bell |
| R2-2311004 | Extension of unified TCI framework for mTRP | Huawei, HiSilicon |
| R2-2311128 | Discussion on remaining issues on Unified TCI framework extension | NTT DOCOMO INC., |
| 7.20.4 | Other | |
| R2-2311005 | Overlapping UL grants handling for STxMP | Huawei, HiSilicon |
| R2-2311130 | Discussion on overlapping UL grants in STxMP | NTT DOCOMO, INC. |
| R2-2311165 | On other than 2TA parameters MIMOevo Rel18 | Ericsson |
| 7.21.1 | Organizational | |
| R2-2309420 | LS on further clarifications on enhancements to realize increasing UE power high limit for CA and DC (R1-2308561; contact: Nokia) | RAN1 |
| R2-2309468 | LS on enhancements to realize increasing UE power high limit for CA and DC (R4-2314728; contact: Nokia) | RAN4 |
| R2-2310196 | Summary of [Post123][802][R18CEenh-CP] CP open issues (HW) | Huawei, HiSilicon |
| R2-2310197 | RRC Running CR for R18 NR coverage enhancements | Huawei, HiSilicon |
| R2-2310475 | Running CR to 38.300 for Rel-18 coverage enhancements | China Telecom |
| R2-2310669 | Report of [Post123][801][CE_enh] UP running CR and open issue discussion (ZTE) | ZTE Corporation, Sanechips |
| R2-2310670 | Draft running CR to 38.321 for Rel-18 coverage enhancement | ZTE Corporation, Sanechips |
| 7.21.2 | Control plane issues | |
| R2-2309591 | Discussion on Coverage Enhancements CP | Ericsson |
| R2-2309699 | Remaining CP issues for Msg1 repetition | CATT |
| R2-2309776 | Remaining control plane issues of further NR Coverage Enhancements | Samsung Electronics Co., Ltd |
| R2-2310198 | Remaining issues of CP aspects for CE | Huawei, HiSilicon |
| R2-2310284 | Discussion on the remaining CP issues for CE | NEC Corporation. |
| R2-2310605 | Discussion on Signalling aspects for Msg1 repetition | LG Electronics Inc. |
| R2-2310671 | Consideration on RRC signalling design for CE | ZTE Corporation, Sanechips |
| R2-2311189 | Considerations on PRACH repetition | Nokia, Nokia Shanghai Bell |
| R2-2311601 | [DRAFT] Reply LS on delta power class | Nokia |
| R2-2311611 | Reply LS on delta power class | RAN2 |
| 7.21.3 | User plane issues | |
| R2-2309570 | Discussion on RAN2 Impacts of DWS and DPC Reporting | vivo |
| R2-2309571 | Discussion on Remaining Issues for PRACH Repetition | vivo |
| R2-2309592 | Discussion on Coverage Enhancements UP | Ericsson |
| R2-2309698 | Discussion on PHR for assumed PUSCH | CATT |
| R2-2309760 | Discussion on PHR for dynamic waveform switching | Xiaomi |
| R2-2309777 | Remaining user plane issues of further NR Coverage Enhancements | Samsung Electronics Co., Ltd |
| R2-2310199 | Remaining issues of UP aspects for CE | Huawei, HiSilicon |
| R2-2310228 | Discussion on power domain enhancements for coverage enhancement | China Telecom |
| R2-2310232 | DWS L2 impacts | InterDigital |
| R2-2310285 | Discussion on the remaining UP issues for CE | NEC Corporation. |
| R2-2310606 | RA procedure for Msg1 repetition | LG Electronics Inc. |
| R2-2310672 | Remaining UP issues for CE | ZTE Corporation, Sanechips |
| R2-2310974 | Open Issues in Coverage Enhancements UP | Qualcomm Incorporated |
| R2-2310975 | PHR enhancements for Coverage Enhancement | Qualcomm Incorporated |
| R2-2311190 | Impacts from waveform switching | Nokia, Nokia Shanghai Bell |
| R2-2311614 | [DRAFT] LS to RAN1 on PHR reporting | InterDigital |
| R2-2311616 | LS to RAN1 on PHR reporting | RAN2 |
| 7.22.1 | Organizational | |
| R2-2309492 | Summary of [Post123][060][LPWUS] Low-power receiver in RRC Connected (Qualcomm) | Qualcomm Incorporated |
| R2-2309737 | Update of TR 38.869 for LP-WUS WUR | vivo (Rapporteur) |
| 7.22.2 | Idle Inactive Mode | |
| R2-2309493 | Use of low-power receiver in RRC Idle/Inactive | Qualcomm Incorporated |
| R2-2309536 | Discussion on LP-WUS in RRC_IDLE/INACTIVE | OPPO |
| R2-2309735 | Discussion on LP-WUS WUR in RRC_IDLE INACTIVE | vivo |
| R2-2309818 | Further considerations on LP-WUS in RRC_IDLE&INACTIVE states | CATT |
| R2-2309858 | LP-WUS in RRC_IDLE/INACATIVE | LG Electronics Inc. |
| R2-2310039 | General considerations on the procedure for RRC_IDLE_INACTIVE | Xiaomi Communications |
| R2-2310062 | Discussion on LPWUS in RRC_IDLE INACTIVE | NEC Corporation. |
| R2-2310313 | RAN2 impact of LP-WUS in RRC_IDLE/INACTIVE state | Apple |
| R2-2310483 | Remaining issues on LP-WUS in RRC_IDLE/INACTIVE state | Huawei, HiSilicon |
| R2-2310722 | LP-WUS in RRC IDLE and INACTIVE | Nokia, Nokia Shanghai Bell |
| R2-2310778 | Considerations on LP-WUR in RRC Idle/Inactive mode | Sony |
| R2-2310827 | Remaining issues of LP-WUS in idle or inactive mode | ZTE Corporation, Sanechips |
| R2-2311064 | LP-WUS/WUR for RRC Idle and Inactive | Ericsson |
| R2-2311171 | On impact to IDLE/INACTIVE procedures to support LP-WUR | Samsung R&D Institute India |
| R2-2311216 | LP-WUS in RRC Idle/ Inactive Mode | Lenovo |
| R2-2311336 | Summary of [AT123bis][510][LP-WUS] connected mode (vivo) | vivo |
| 7.22.3 | Connected Mode | |
| R2-2309530 | Discussion on LP-WUS in RRC Connected | OPPO |
| R2-2309736 | Discussion on LP-WUS WUR in RRC_Connected | vivo |
| R2-2309819 | LP-WUS co-existence with DCP in RRC_CONNECTED state | CATT |
| R2-2309842 | Further considerations on LP-WUS in RRC_CONNECTED | Huawei, HiSilicon |
| R2-2310040 | Discussing on LP-WUS monitoring for RRC_Connected | Xiaomi Communications |
| R2-2310061 | Discussion on LPWUS in RRC_CONNECTED | NEC Corporation. |
| R2-2310314 | RAN2 impact of LP-WUS in RRC_CONNECTED state | Apple |
| R2-2310442 | Discussion on LP-WUS for Connected | LG Electronics Inc. |
| R2-2310828 | Remaining issues of LP-WUS in connected mode | ZTE Corporation, Sanechips |
| R2-2310877 | On Low-power WUS in RRC_CONNECTED | Nokia, Nokia Shanghai Bell |
| R2-2311068 | LP-WUS/WUR for RRC Connected | Ericsson |
| R2-2311172 | On impact to Connected mode procedures to support LP-WUR | Samsung R&D Institute India |
| R2-2311217 | LP-WUS in RRC Connected Mode | Lenovo |
| 7.23.1 | Organizational | |
| R2-2310689 | Stage 2 running CR on timing resiliency and URLLC | Nokia, Nokia Shanghai Bell |
| R2-2310785 | Introduction of URLLC and Timing Resiliency | Ericsson |
| R2-2310907 | Summary of [POST123][309][R18 URLLC]RunningCR_38.331 | Ericsson |
| 7.23.2 | General | |
| R2-2309526 | Remaining issues of timing synchronization status and reporting | Xiaomi |
| R2-2309563 | Remaining Issues for Timing Synchronization Status and Reporting | vivo |
| R2-2309765 | Discussion on TSS clock quality information | Huawei, HiSilicon |
| R2-2310254 | Discussion on the network timing synchronization status monitoring | CMCC |
| R2-2310329 | Remaining open issues for timing synchronization | Apple |
| R2-2310480 | Remaining Issues on Timing Synchronization | Samsung |
| R2-2310690 | 5GS network timing synchronization status and reporting | Nokia, Nokia Shanghai Bell |
| R2-2310834 | Remaining issues of acquiring time synchronization status | ZTE Corporation, Sanechips |
| R2-2310976 | Open Issues in Clock Quality Reporting | Qualcomm Incorporated |
| 7.24.1 | TEI proposals by Other Groups | |
| R2-2309405 | Reply LS on Mitigation of Downgrade attacks (C1-236517; contact: Orange) | CT1 |
| R2-2309436 | LS on SDT signalling optimization for partial context transfer (R3-234589; contact: Qualcomm) | RAN3 |
| R2-2310617 | Network support and clarification of redirection to 3G | Vodafone GmbH |
| R2-2310625 | Status of discussion on Redirections and Reselections to GERAN | Vodafone GmbH |
| R2-2310658 | Network support and clarification of redirection to 3G | Vodafone, Orange, Deutsche Telekom, AT&T, Verizon |
| R2-2310726 | SDT signalling optimization for partial context transfer | Huawei, HiSilicon, China Telecom, Qualcomm, CATT, Lenovo |
| R2-2310814 | Reply LS on SDT signalling optimization for partial context transfer | Qualcomm Incorporated |
| R2-2311191 | Non-SDT DL data arrival without anchor relocation | Nokia, Nokia Shanghai Bell |
| 7.24.2 | TEI proposals by RAN2 | |
| R2-2309415 | Reply LS on longer CG-SDT periodicities (R1-2308487; contact: NTT DOCOMO) | RAN1 |
| R2-2309441 | LS on RedCap UE MBS Broadcast reception (R3-234735; contact: ZTE) | RAN3 |
| R2-2309560 | Discussion on PTM retransmission reception by UEs without HARQ feedback | CATT |
| R2-2309684 | Discussion on emergency cause value for SL Relay | OPPO |
| R2-2309688 | Remaining CP issues on MT-SDT | LG Electronics Inc. |
| R2-2309795 | Discussion on MUSIM paging cause forwarding | vivo |
| R2-2310096 | Enhanced IF measurement report information | Lenovo |
| R2-2310107 | Extended periodicity for CG-SDT | ZTE Corporation, Sanechips |
| R2-2310161 | Correction to flightPathInfoAvailable when connected to 5GC | Qualcomm Incorporated |
| R2-2310237 | Discussion on longer periodicity for CG-SDT | NEC Corporation. |
| R2-2310280 | 38331CR to introduce measurement sequence | CMCC, Ericsson |
| R2-2310281 | 38306CR to introduce measurement sequence | CMCC, Ericsson |
| R2-2310527 | Discussion on UE behaviours of delay measurements upon MO updates | Huawei, HiSilicon |
| R2-2310544 | Discussion on issues for SFN-DFN offset procedure in 38.331 | ZTE Corporation |
| R2-2310596 | Enhancing SCell A2 event reporting [TEI] | KDDI Corporation, Ericsson, NTT Docomo, BT Plc., AT&T |
| R2-2310698 | Configuration of cell individual offset in ReportConfig | NTT Docomo, Ericsson, KDDI corporation, BT Plc., AT&T, Orange, Turkcell |
| R2-2310718 | Clarification on RedCap CFR configuration for MBS Broadcast | Huawei, HiSilicon |
| R2-2310719 | Correction on RedCap CFR configuration | Huawei, HiSilicon |
| R2-2310720 | Discussion on enabling PTM retransmission reception by UEs with HARQ disabled | Huawei, HiSilicon |
| R2-2310728 | Discussion on CG-SDT enhancements | Huawei, HiSilicon |
| R2-2310829 | Discussion on unpredictable inter-frequency measurement reporting | MediaTek Inc. |
| R2-2310853 | Adding support for Bluetooth AoA/AoD | Ericsson, AT&T, Polaris Wireless, u-blox, T-Mobile |
| R2-2310855 | Forwarding on posSIBs relaying to remote UE [PosL2RemoteUE] | Ericsson |
| R2-2310901 | Steering stationary and low mobility UEs in FR2 | Ericsson, Verizon |
| R2-2310979 | Introduction of longer periodicities for CG-SDT [Longer-Periodicites-CG-SDT] | Ericsson, Intel Corporation |
| R2-2310981 | Introduction of longer periodicities for CG-SDT [Longer-Periodicites-CG-SDT] | Ericsson, Intel Corporation |
| R2-2310992 | PTM retransmission reception for multicast DRX with HARQ feedback disabled | Nokia, Nokia Shanghai Bell, AT&T, Qualcomm, Samsung, Verizon, Ericsson |
| R2-2310993 | PTM retransmission reception for multicast DRX with HARQ feedback disabled] | Nokia, Nokia Shanghai Bell, AT&T, Qualcomm, Samsung, Verizon, Ericsson |
| R2-2311026 | Considerations on voice and video support for Relays | Philips International B.V., FirstNet, InterDigital, KPN, TNO |
| R2-2311106 | Enhancing SCell A2 event reporting [TEI] | KDDI Corporation, Ericsson, NTT Docomo, BT Plc., AT&T, Turkcell |
| R2-2311218 | Corrections on RedCap CFR for MBS broadcast | Beijing Xiaomi Mobile Software |
| R2-2311221 | Configuration of cell individual offset in ReportConfig | NTT Docomo, Ericsson, KDDI corporation, BT Plc., AT&T, Orange, Turkcell, Deutsche Telekom |
| R2-2311248 | Further clarification on RedCap CFR for MBS Broadcast [RedCapMBS_Bcast] | Qualcomm Incorporated |
| R2-2311266 | PTM retransmission reception for multicast DRX with HARQ feedback disabled [PTM_ReTx_Mcast_HARQ_Disb] | Nokia, Nokia Shanghai Bell, AT&T, Qualcomm, Samsung, Verizon, Ericsson |
| R2-2311267 | PTM retransmission reception for multicast DRX with HARQ feedback disabled [PTM_ReTx_Mcast_HARQ_Disb] | Nokia, Nokia Shanghai Bell, AT&T, Qualcomm, Samsung, Verizon, Ericsson |
| R2-2311268 | PTM retransmission reception for multicast DRX with HARQ feedback disabled [PTM_ReTx_Mcast_HARQ_Disb] | Nokia |
| R2-2311393 | [AT123bis][430][TEI18] Relay emergency cause value (OPPO) | OPPO |
| R2-2311394 | [AT123bis][431][TEI18] Bluetooth AoA/AoD positioning (Ericsson) | Ericsson |
| R2-2311395 | [AT123bis][432][TEI18] Positioning for remote Ues | ZTE Corporation |
| R2-2311575 | [DRAFT] LS on extended CG-SDT periodicities | Ericsson |
| R2-2311588 | LS on extended CG-SDT periodicities | RAN2 |
| R2-2311600 | LS to CT1 on emergency cause value for relay | RAN2 |
| 7.25.1 | RAN4 led items | |
| R2-2309418 | Reply LS on UE features for NR ATG (R1-2308531; contact: CMCC) | RAN1 |
| R2-2309446 | LS on lower MSD capability (R4-2312247; contact: Huawei) | RAN4 |
| R2-2309449 | Reply LS on MAC-CE Based Indication for Cross-RRH TCI State Switch (R4-2314299; contact: Nokia) | RAN4 |
| R2-2309450 | LS on FR2 SCell activation enhancements (R4-2314338; contact: Apple) | RAN4 |
| R2-2309456 | LS on NR ATG network assistance and TA reporting (R4-2314450; contact: CMCC) | RAN4 |
| R2-2309459 | Reply LS on measurements without gaps (R4-2314457; contact: Nokia) | RAN4 |
| R2-2309463 | LS on UE indication of FR2 multi-RX operation (R4-2314478; contact: Apple) | RAN4 |
| R2-2309464 | LS on Dual TCI state switching in mDCI (R4-2314479; contact: Ericsson) | RAN4 |
| R2-2309466 | Reply LS on non-simultaneous UL and DL from different two bands during UL CA (R4-2314656; contact: CATT) | RAN4 |
| R2-2309471 | LS on signaling support for ATG UE (R4-2314926; contact: Apple) | RAN4 |
| R2-2309472 | LS on signaling support for intra-band non-collocated NR-CA,EN-DC (RP-232692; contact: KDDI) | RAN |
| R2-2309513 | Discussion on MSD Capability | OPPO |
| R2-2309521 | Discussion on model for L2 triggered L3 measurement report | Xiaomi |
| R2-2309522 | Introduction of FR2 SCell enhancements | Xiaomi |
| R2-2309577 | RAN2 Impacts of Cross-RRH TCI State Switch | vivo |
| R2-2309687 | Discussion on BS signaling support for (non-)collocated scenarios | OPPO |
| R2-2309694 | Discussion on open issues of ATG | CATT |
| R2-2309695 | Discussion on the support of lower MSD | CATT |
| R2-2309696 | Discussion on UE indication of FR2 multi-RX operation | CATT |
| R2-2309738 | Introduction of support for BWP operation without restriction | vivo, Vodafone, ZTE Corporation, Sanechips |
| R2-2309739 | Introduction of support for BWP operation without restriction | vivo, Vodafone, ZTE Corporation, Sanechips |
| R2-2309740 | Introduction of support for BWP operation without restriction | vivo, Vodafone, ZTE Corporation, Sanechips |
| R2-2309761 | Discussion on the support of ATG | Xiaomi |
| R2-2309820 | Introduction of intra-band non-collocated NR-CA,EN-DC | KDDI Corporation |
| R2-2309821 | Introduction of intra-band non-collocated NR-CA,EN-DC | KDDI Corporation |
| R2-2309853 | Discussions on Signaling Support for Intra-band Non-Collocated NR-CA, EN-DC | Samsung |
| R2-2309854 | Signaling support for intra-band non-collocated NR-CA, EN-DC | Samsung |
| R2-2309855 | Signaling support for intra-band non-collocated NR-CA, EN-DC | Samsung |
| R2-2309861 | Reply LS on Dual TCI state switching in mDCI | Nokia Corporation |
| R2-2310134 | Discussion on RAN4 LS on MAC-CE Based Indication for Cross-RRH TCI State Switch | Ericsson |
| R2-2310135 | Introduction of Cross-RRH TCI State Switch indication in MAC spec for high speed train | Ericsson |
| R2-2310136 | Introduction of Cross-RRH TCI State Switch indication in RRC for high speed train | Ericsson |
| R2-2310137 | Introduction of UE capability on Cross-RRH TCI State Switch indication for high speed train | Ericsson |
| R2-2310185 | TA report in air to ground access | Qualcomm Incorporated |
| R2-2310186 | Discussion on UE capability for ATG | Qualcomm Incorporated |
| R2-2310187 | Introduction of ATG UE | Qualcomm Incorporated |
| R2-2310252 | TS 38.331 RRC Running CR for NR ATG Rel-18 | CMCC |
| R2-2310253 | Considerations on RAN2 Signalling Design of ATG per RAN4 LSs | CMCC |
| R2-2310316 | FR2 SCell Enhancement | Apple |
| R2-2310317 | Discussion on ATG | Apple |
| R2-2310320 | Discussion on intra-band non-collocated ENDC/NR SA | Apple |
| R2-2310321 | UE indication of FR2 multi-RX operation | Apple |
| R2-2310322 | Introduction on UE preference on multi-Rx operation in UAI | Apple |
| R2-2310340 | Handling Rel-17 DC location signaling enhancement | Apple |
| R2-2310362 | Discussion on further measurement gap enhancement | MediaTek Inc. |
| R2-2310393 | Introduction of measurements without gap with interruption | MediaTek Inc., Huawei, HiSilicon |
| R2-2310395 | Introduction of measurements without gap with interruption | MediaTek Inc., Huawei, HiSilicon |
| R2-2310397 | Running CR for further measurement gap enhancements | MediaTek Inc., Huawei, HiSilicon |
| R2-2310403 | Running CR for further measurement gap enhancements capabilities | MediaTek Inc., Huawei, HiSilicon |
| R2-2310404 | Running CR for further measurement gap enhancements capabilities | MediaTek Inc., Huawei, HiSilicon |
| R2-2310414 | Discussion on UE indication of FR2 multi-RX operation | Huawei, HiSilicon |
| R2-2310424 | Discussion on inter-RAT measurements without gaps | vivo |
| R2-2310425 | Discussion on lower MSD signalling | vivo |
| R2-2310489 | Remaining issues on FR2 SCell activation enhancement | Huawei, HiSilicon |
| R2-2310495 | Enhancements for Unknown FR2 SCell activation | Qualcomm Incorporated |
| R2-2310522 | Discussion on MAC-CE based indication for cross-RRH TCI state switch | Huawei, HiSilicon, Samsung |
| R2-2310523 | Introduction of HST FR2 Enhanced TCI State Switch for 38.321 | Huawei, HiSilicon, Samsung |
| R2-2310524 | Introduction of HST FR2 Enhanced TCI State Switch for 38.331 | Huawei, HiSilicon, Samsung |
| R2-2310525 | Introduction of HST FR2 Enhanced TCI State Switch for 38.306 | Huawei, HiSilicon, Samsung |
| R2-2310588 | The UE capability signaling for lower MSD | Xiaomi |
| R2-2310593 | Discussion on singling design for Non-collocated feature | KDDI Corporation |
| R2-2310631 | On air-to-ground system information and NTN adaptations | Samsung Electronics Polska |
| R2-2310632 | Further View on Air-To-Ground (ATG) in Rel-18 | Nokia, Nokia Shanghai Bell |
| R2-2310675 | Discussion on ATG | ZTE Corporation, Sanechips |
| R2-2310676 | Discussion on FR2 unknown SCell activation | ZTE Corporation, Sanechips |
| R2-2310677 | Discussion on Cross RRH TCI state switch | ZTE Corporation, Sanechips |
| R2-2310678 | Discussion on MGE | ZTE Corporation, Sanechips |
| R2-2310733 | Discussion on DC location enhancement | Huawei, HiSilicon |
| R2-2310734 | Discussion on lower MSD capability | Huawei, HiSilicon |
| R2-2310735 | Introduction of lower MSD capability | Huawei, HiSilicon |
| R2-2310736 | Introduction of lower MSD capability | Huawei, HiSilicon |
| R2-2310737 | Introduction of signalling support for intra-band non-collocated NR-CA,EN-DC | Huawei, HiSilicon |
| R2-2310738 | Introduction of signalling support for intra-band non-collocated NR-CA,EN-DC | Huawei, HiSilicon |
| R2-2310798 | Cross RRH TCI state switch | Nokia, Nokia Shanghai Bell |
| R2-2310799 | Scell activation and L3 reporting | Nokia, Nokia Shanghai Bell |
| R2-2310800 | Using non-simultaneous UL and DL from different two bands during UL CA | Nokia, Nokia Shanghai Bell |
| R2-2310900 | Introduction of FR2 SCell enhancements | Ericsson |
| R2-2310951 | Support of lower MSD capability | Ericsson |
| R2-2310952 | Impact of non-simultaneous DL and UL | Ericsson |
| R2-2310953 | RAN2 updates for DSS | Ericsson, ZTE Corporation |
| R2-2310954 | Running 38.331 CR for R18 DSS | Ericsson, ZTE Corporation |
| R2-2310955 | Signaling support for intra-band NR-CA and inter-band EN-DC | Ericsson |
| R2-2311044 | Consideration on Lower MSD Capability Signaling | ZTE Corporation, Sanechips |
| R2-2311126 | Discussion on SI for ATG | Ericsson |
| R2-2311155 | Introduction on UE preference for multi-Rx operation in UAI | Apple |
| R2-2311156 | Introduction of FR2 SCell enhancements | Apple |
| R2-2311164 | Introduction on UE preference on multi-Rx operation in UAI | Apple |
| R2-2311180 | Response to LS on Dual TCI state switching in mDCI | Ericsson |
| R2-2311288 | DRAFT Response LS to LS on Dual TCI state switching in mDCI | Ericsson |
| R2-2311571 | Offline discussion summary for Non-collocated signaling | KDDI Corporation |
| R2-2311579 | [DRAFT] LS on power class indication in lower MSD capability | Qualcomm Incorporated |
| R2-2311586 | LS on power class indication in lower MSD capability | RAN2 |
| R2-2311592 | DRAFT Response LS to LS on Dual TCI state switching in mDCI | Ericsson |
| R2-2311594 | Response LS to LS on Dual TCI state switching in mDCI | RAN2 |
| R2-2311615 | Reply LS to Reply LS on MAC-CE Based Indication for Cross-RRH TCI State | RAN2 |
| R2-2311619 | Reply LS to Reply LS on MAC-CE Based Indication for Cross-RRH TCI State | RAN2 |
| 7.25.2 | RAN1 led items | |
| R2-2309514 | Left issue on Tx Switching | OPPO |
| R2-2309917 | Remaining issues on UL TX switching and multi-cell scheduling for multi-carrier enhancement | CATT |
| R2-2310490 | Remaining issues on Rel-18 UL Tx switching enhancements | Huawei, HiSilicon, CMCC |
| R2-2310491 | Capturing RAN2 agreements in RRC configuration CR for Rel-18 UL Tx switching enhancements | Huawei, HiSilicon, NTT DOCOMO INC. |
| R2-2310492 | Clarification on MIMO layer reporting for 1Tx-1Tx switching | Huawei, HiSilicon, NTT DOCOMO INC. |
| R2-2310673 | Running 38.306 CR for R18 DSS | ZTE Corporation, Ericsson |
| R2-2310674 | Discussion on remaining issues of Rel-18 UL Tx switching | ZTE Corporation, Sanechips |
| R2-2310959 | Running 38.331 CR for R18 DSS | Ericsson, ZTE Corporation |
| R2-2311131 | Draft 38.331 CR for introduction of multi-cell PDSCH_PUSCH scheduling | NTT DOCOMO, INC., Huawei, HiSilicon |
| R2-2311134 | Discussion on remaining issues on UL Tx switching | NTT DOCOMO, INC. |
| 7.25.3 | Other | |
| R2-2309403 | LS on usage of paging subgrouping information in RAN in case of abnormal scenario (C1-235673; contact: Huawei) | CT1 |
| R2-2310518 | Discussion on NAS-AS interaction of NS-AoS | Huawei, HiSilicon |
| R2-2310519 | Introduction of NAS-AS interaction of NS-AoS for TS 38.304 | Huawei, HiSilicon |
| R2-2310520 | Introduction of NAS-AS interaction of NS-AoS for TS 38.331 | Huawei, HiSilicon |
| R2-2310521 | Introduction of NAS-AS interaction of NS-AoS for TS 38.300 | Huawei, HiSilicon |
| R2-2310817 | Draft CR to TS 38.300 on introduction of R18 eNPN | China Telecom |
| R2-2310818 | Draft CR to TS 38.306 on introduction of R18 eNPN | China Telecom, Lenovo |
| R2-2310854 | On the Positioning Reference Units aspects [PRU] | Ericsson, vivo |
| R2-2310920 | Clarification of PRU measurement reporting | Qualcomm Incorporated |
| 7.25.4 | Self-Evaluation NTN | |
| R2-2309714 | Report of [Post123][102]NTN Self Ev] CPUP latency (Ericsson) | Ericsson |
| R2-2310086 | Discussion on IMT-2020 Satellite self-evaluation for Latency | THALES |
| R2-2311112 | CP and UP latency evaluation TP | Qualcomm Technologies Ireland |
| R2-2311215 | [Draft] LS to RAN1 on RAN2 progress of NTN Self Evaluation | Huawei, HiSilicon |
| R2-2311233 | Satellite IMT-2020 self-evaluation: CP latency | Ericsson |
| R2-2311234 | Satellite IMT-2020 self-evaluation: UP latency | Ericsson |
| R2-2311314 | TP for TR 37.911 | Ericsson |
| R2-2311315 | LS to RAN1 on RAN2 progress of NTN Self Evaluation | RAN2 |
| 8.1 | Session on LTE V2X and NR SL | |
| R2-2311271 | Report from session on LTE V2X and NR SL | Vice Chairman (Samsung) |
| 8.2 | Session on NR MIMO evolution and Multi-SIM | |
| R2-2311272 | Report from session on NR MIMO evolution and Multi-SIM’ | Vice Chairman (CATT) |
| 8.3 | Session on NR NTN and IoT NTN | |
| R2-2311273 | Report from Break-Out Session on NR NTN and IoT NTN | Session chair (ZTE) |
| 8.4 | Session on Mobility Enh, Mobile IAB and LP-WUS | |
| R2-2311274 | Report from session on Mobility Enh, Mobile IAB and LP-WUS | Session chair (MediaTek) |
| 8.5 | Session on positioning and sidelink relay | |
| R2-2311275 | Report from session on positioning and sidelink relay | Session chair (MediaTek) |
| 8.6 | Session on SON/MDT | |
| R2-2311276 | Report from SON/MDT session | Session chair (CMCC) |
| 8.7 | Session on MBS, QoE and LTE legacy | |
| R2-2311277 | Report from session on MBS, QoE and LTE legacy | Session chair (Huawei) |
| 8.8 | Session on IDC | |
| R2-2311278 | Report from IDC breakout session | Session chair (Intel) |
| 8.9 | Session on NC Repeater | |
| R2-2311279 | Report from NC Repeater breakout session | Session chair (Apple) |
| 8.10 | Session on maintenance and eRedCap | |
| R2-2311280 | Report from maintenance and eRedCap breakout session | Session chair (Ericsson) |
| 8.11 | Session on Further NR coverage enhancements | |
| R2-2311281 | Report from Further NR coverage enhancements session | Session chair (ZTE) |